Load Balancing DNS

[Madhan Singh]

Hi
I am deploying my ASP.Net web application in two different servers I want to
apply or configure those server with load balancing technique (i.e Round
Robin DNS)

 

[Jmnts]

Hi

- Create two A records with the same name and different IpAddress (Example:
AppServer.domain.com-192.168.0.1, AppServer.domain.com-192.168.0.2)

- Create a CNAME (Canonical Name) that points to the A record
(AppServer.domain.com), note you only need to add the alias name, for
example: your domain is domain.com, and the app is refered by App, then your
alias should be App, it stays (App.domain.com)

- To enable round and robin, right click dns server choose properties,
advanced tab and choose enable round and robin.

That should do the job.

 

[Madhan Singh]

Hi
Thanks. But I am have a doubt could you pls clarify me. Since I am a
beginner I am having the problem to implement that. Could you pls say me how
should I asssign the CNAME and how to set the properties.
Regards,

 

[Jmnts]

Hi
Right click in the Domain folder (Under Dns Forward LookUp Zones) and choose
new -> Alias (CNAME).

For example:
You have a domain named: Domain.com, right click the domain name and choose
new Alias, then in the first textbox write App, then choose the target host,
as I aready mention you shoul coose one of the 2 A records created
(AppServer.domain.com)

For more inf check:
How To Configure DNS Records for Your Web Site in Windows Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;324260

 

[Madhan Singh]

Ok I wil try and mail you after i get my result..
Thanks & Regards

 

[Herb Martin]

Ok I wil try and mail you after i get my result..
Thanks & Regards

CNAMES are NOT used for load balancing, i.e., Round Robin.

CNAMEs would give you multiple NAMES for a single
computer name.

You need A records for Round Robin: Multiple ADDRESSES
for the SAME name.

 

[Jmnts]

Hi Herb that's what I said in previous post (Create two A records with the
same name and different IpAddress, then map CNAME for one that A records,
has the A records have the same name the Round and Robin will work, right?)
Did you read ?

He needs Round and robin for two different servers....

--
Best Regards
Systems Administrator
MCSA + Exchange

Ok I wil try and mail you after i get my result..
Thanks & Regards

CNAMES are NOT used for load balancing, i.e., Round Robin.

CNAMEs would give you multiple NAMES for a single
computer name.

You need A records for Round Robin: Multiple ADDRESSES
for the SAME name.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Kevin D. Goodknecht Sr. [MVP]]

Hi Herb that's what I said in previous post (Create two A records
with the same name and different IpAddress, then map CNAME for one
that A records, has the A records have the same name the Round and
Robin will work, right?) Did you read ?

He needs Round and robin for two different servers....

I think the point Herb is getting at is the CNAME record is unnecessary. You
can make many A records with the same name and different IPs, and round
robin will rotate the records. Adding a CNAME adds an extra lookup to
resolve the CNAME. One would want to use a CNAME if there are going to be
multiple alias names for the same site, which is irrelevant to the OP's
original question. It only adds confusion to the issue by making the OP
think all they need is a CNAME, the problem with this is, there can only be
one CNAME on a node and CNAMES are incompatible with other records on the
same node.

 

[Herb Martin]

I think the point Herb is getting at is the CNAME record is unnecessary.
You
can make many A records with the same name and different IPs, and round
robin will rotate the records.

Yes, sort of -- I am specifically saying that the round robin
requires the use of A records.

The CNAME is something you add later IF you wish to give
the machines a DIFFERENT name than the A records you
already used for Round Robin and (as Kevin says below)....

Adding a CNAME adds an extra lookup to
resolve the CNAME.

....and while adding this CNAME record to change a MACHINE'S
REAL NAME into a standard (canonical) name (webserver99 into
www) makes sense it isn't likely to make as much sense in the
round robin case since you already must pick a COMMON name
for the A records -- if you do that, the common name might as well
be the standard-canonical (e.g., WWW) name.

One would want to use a CNAME if there are going to be
multiple alias names for the same site,

Correct. And if there are multiple sites on this server then
again we may end up with CNAMEs

My point (as Kevin indicates) were that the Round Robin feature
was UNRELATED to the CNAMES and dependent on multiple
A records.

which is irrelevant to the OP's
original question. It only adds confusion to the issue by making the OP
think all they need is a CNAME, the problem with this is, there can only
be
one CNAME on a node and CNAMES are incompatible with other records on the
same node.

 

[Jmnts]

Let me explain:
Of course if you place 2 A records, that will work to.

My solution was in future growth in mind.

You see if in future Madhan has for example:
5 different web applications mapped to 10 web servers:

According with your solution he will have to have 5 different A records for
each web server. (50 A records in total) Right?

App1.domain.com - > 192.168.0.1
App1.domain.com - > 192.168.0.2
App1.domain.com - > 192.168.0.3
App1.domain.com - > 192.168.0.4
App1.domain.com - > 192.168.0.5
App1.domain.com - > 192.168.0.6
App1.domain.com - > 192.168.0.7
App1.domain.com - > 192.168.0.8
App1.domain.com - > 192.168.0.9
App1.domain.com - > 192.168.0.10

App2.domain.com - > 192.168.0.1
App2.domain.com - > 192.168.0.2
App2.domain.com - > 192.168.0.3
App2.domain.com - > 192.168.0.4
App2.domain.com - > 192.168.0.5
etc , and so on ...

According to mine solution he only needs to map 5 different CNAME records,
one for each App, and one A record for each server (5 Cname records + 10 A
records one for each Webserver= 15 records right?).


Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A records
for each web server. (more 50 A records. in total he will have 50+50=100 A
records) Right?
According to mine solution he only needs to map 5 different CNAME records to
the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe), clustering,
Nlb,etc.
But I'm only try to explain how CNAME could be a better work Methodology ( I
think).

Please post if you don't agree with that, state your reasons. Just remember
we're talking about Round and Robin solutions, Not Clustering or any other.

--
Best Regards
Systems Administrator
MCSA + Exchange

Hi Herb that's what I said in previous post (Create two A records with
the same name and different IpAddress, then map CNAME for one that A
records, has the A records have the same name the Round and Robin will
work, right?)
Did you read ?

He needs Round and robin for two different servers....

--
Best Regards
Systems Administrator
MCSA + Exchange

Hi
Thanks. But I am have a doubt could you pls clarify me. Since I am
a beginner I am having the problem to implement that. Could you pls
say me how should I asssign the CNAME and how to set the properties.
Regards,

Ok I wil try and mail you after i get my result..
Thanks & Regards

CNAMES are NOT used for load balancing, i.e., Round Robin.

CNAMEs would give you multiple NAMES for a single
computer name.

You need A records for Round Robin: Multiple ADDRESSES
for the SAME name.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Hi
Right click in the Domain folder (Under Dns Forward LookUp Zones) and
choose new -> Alias (CNAME).

For example:
You have a domain named: Domain.com, right click the domain name and
choose new Alias, then in the first textbox write App, then choose the
target host, as I aready mention you shoul coose one of the 2 A records
created (AppServer.domain.com)

For more inf check:
How To Configure DNS Records for Your Web Site in Windows Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;324260


--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
Thanks. But I am have a doubt could you pls clarify me. Since I am
a beginner I am having the problem to implement that. Could you pls
say me how should I asssign the CNAME and how to set the properties.
Regards,

Hi

- Create two A records with the same name and different IpAddress
(Example: AppServer.domain.com-192.168.0.1,
AppServer.domain.com-192.168.0.2)

- Create a CNAME (Canonical Name) that points to the A record
(AppServer.domain.com), note you only need to add the alias name, for
example: your domain is domain.com, and the app is refered by App,
then your alias should be App, it stays (App.domain.com)

- To enable round and robin, right click dns server choose
properties, advanced tab and choose enable round and robin.

That should do the job.




--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
I am deploying my ASP.Net web application in two different servers I
want to
apply or configure those server with load balancing technique (i.e
Round
Robin DNS)

 

[Herb Martin]

According to mine solution he only needs to map 5 different CNAME records,

one for each App, and one A record for each server (5 Cname records + 10 A
records one for each Webserver= 15 records right?).

But notice that the CNAME records have NOTHING to do
with load balancing or Round Robin.

Load balancing through round robin is strictly an A record issue.

Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A
records for each web server. (more 50 A records. in total he will have
50+50=100 A records) Right?
According to mine solution he only needs to map 5 different CNAME records
to the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe), clustering,
Nlb,etc.
But I'm only try to explain how CNAME could be a better work Methodology
( I think).

CNAMES have nothing directly to do with load balancing
or clustering/NLB either.

Please post if you don't agree with that, state your reasons. Just
remember we're talking about Round and Robin solutions, Not Clustering or
any other.

Multiple A records provide load balancing amoung EACH
of the addresses associated with each A record -- since the
DNS rotates the order returned to the client and clients tend
to "pick off the top of the list".

CNAME records MERELY provide alternative names for
some (existing) A record name.

CNAME records may be useful in a solution but are irrelevant
to the LOAD BALANCING part as they merely give you
multiple names for the same IP address.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Let me explain:
Of course if you place 2 A records, that will work to.

My solution was in future growth in mind.

You see if in future Madhan has for example:
5 different web applications mapped to 10 web servers:

According with your solution he will have to have 5 different A records
for each web server. (50 A records in total) Right?

App1.domain.com - > 192.168.0.1
App1.domain.com - > 192.168.0.2
App1.domain.com - > 192.168.0.3
App1.domain.com - > 192.168.0.4
App1.domain.com - > 192.168.0.5
App1.domain.com - > 192.168.0.6
App1.domain.com - > 192.168.0.7
App1.domain.com - > 192.168.0.8
App1.domain.com - > 192.168.0.9
App1.domain.com - > 192.168.0.10

App2.domain.com - > 192.168.0.1
App2.domain.com - > 192.168.0.2
App2.domain.com - > 192.168.0.3
App2.domain.com - > 192.168.0.4
App2.domain.com - > 192.168.0.5
etc , and so on ...

According to mine solution he only needs to map 5 different CNAME records,
one for each App, and one A record for each server (5 Cname records + 10 A
records one for each Webserver= 15 records right?).


Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A
records for each web server. (more 50 A records. in total he will have
50+50=100 A records) Right?
According to mine solution he only needs to map 5 different CNAME records
to the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe), clustering,
Nlb,etc.
But I'm only try to explain how CNAME could be a better work Methodology
( I think).

Please post if you don't agree with that, state your reasons. Just
remember we're talking about Round and Robin solutions, Not Clustering or
any other.

--
Best Regards
Systems Administrator
MCSA + Exchange

Hi Herb that's what I said in previous post (Create two A records with
the same name and different IpAddress, then map CNAME for one that A
records, has the A records have the same name the Round and Robin will
work, right?)
Did you read ?

He needs Round and robin for two different servers....

--
Best Regards
Systems Administrator
MCSA + Exchange

Hi
Thanks. But I am have a doubt could you pls clarify me. Since I am
a beginner I am having the problem to implement that. Could you pls
say me how should I asssign the CNAME and how to set the properties.
Regards,


Ok I wil try and mail you after i get my result..
Thanks & Regards

CNAMES are NOT used for load balancing, i.e., Round Robin.

CNAMEs would give you multiple NAMES for a single
computer name.

You need A records for Round Robin: Multiple ADDRESSES
for the SAME name.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Hi
Right click in the Domain folder (Under Dns Forward LookUp Zones) and
choose new -> Alias (CNAME).

For example:
You have a domain named: Domain.com, right click the domain name and
choose new Alias, then in the first textbox write App, then choose the
target host, as I aready mention you shoul coose one of the 2 A
records created (AppServer.domain.com)

For more inf check:
How To Configure DNS Records for Your Web Site in Windows Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;324260


--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
Thanks. But I am have a doubt could you pls clarify me. Since I am
a beginner I am having the problem to implement that. Could you pls
say me how should I asssign the CNAME and how to set the properties.
Regards,

Hi

- Create two A records with the same name and different IpAddress
(Example: AppServer.domain.com-192.168.0.1,
AppServer.domain.com-192.168.0.2)

- Create a CNAME (Canonical Name) that points to the A record
(AppServer.domain.com), note you only need to add the alias name,
for example: your domain is domain.com, and the app is refered by
App, then your alias should be App, it stays (App.domain.com)

- To enable round and robin, right click dns server choose
properties, advanced tab and choose enable round and robin.

That should do the job.




--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
I am deploying my ASP.Net web application in two different servers
I want to
apply or configure those server with load balancing technique (i.e
Round
Robin DNS)

 

[Jmnts]

- But notice that the CNAME records have NOTHING to do with load balancing
or Round Robin. Load balancing through round robin is strictly an A record
issue.

If I was assuming that CNAME records had something to do with Roud and
robin, I wouldn't say that we need to create A records right?


- CNAMES have nothing directly to do with load balancing or clustering/NLB
either.

I never said that CNAME records had something to do with clustering/NLB.


- CNAME records may be useful in a solution but are irrelevant to the LOAD
BALANCING part as they merely give you multiple names for the same IP
address.

I t seems that you don't understand the Admin impact in the scenario that i
gave as example.

--
Best Regards
Systems Administrator
MCSA + Exchange

According to mine solution he only needs to map 5 different CNAME
records, one for each App, and one A record for each server (5 Cname
records + 10 A records one for each Webserver= 15 records right?).

But notice that the CNAME records have NOTHING to do
with load balancing or Round Robin.

Load balancing through round robin is strictly an A record issue.

Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A
records for each web server. (more 50 A records. in total he will have
50+50=100 A records) Right?
According to mine solution he only needs to map 5 different CNAME records
to the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe), clustering,
Nlb,etc.
But I'm only try to explain how CNAME could be a better work Methodology
( I think).

CNAMES have nothing directly to do with load balancing
or clustering/NLB either.

Please post if you don't agree with that, state your reasons. Just
remember we're talking about Round and Robin solutions, Not Clustering or
any other.

Multiple A records provide load balancing amoung EACH
of the addresses associated with each A record -- since the
DNS rotates the order returned to the client and clients tend
to "pick off the top of the list".

CNAME records MERELY provide alternative names for
some (existing) A record name.

CNAME records may be useful in a solution but are irrelevant
to the LOAD BALANCING part as they merely give you
multiple names for the same IP address.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Let me explain:
Of course if you place 2 A records, that will work to.

My solution was in future growth in mind.

You see if in future Madhan has for example:
5 different web applications mapped to 10 web servers:

According with your solution he will have to have 5 different A records
for each web server. (50 A records in total) Right?

App1.domain.com - > 192.168.0.1
App1.domain.com - > 192.168.0.2
App1.domain.com - > 192.168.0.3
App1.domain.com - > 192.168.0.4
App1.domain.com - > 192.168.0.5
App1.domain.com - > 192.168.0.6
App1.domain.com - > 192.168.0.7
App1.domain.com - > 192.168.0.8
App1.domain.com - > 192.168.0.9
App1.domain.com - > 192.168.0.10

App2.domain.com - > 192.168.0.1
App2.domain.com - > 192.168.0.2
App2.domain.com - > 192.168.0.3
App2.domain.com - > 192.168.0.4
App2.domain.com - > 192.168.0.5
etc , and so on ...

According to mine solution he only needs to map 5 different CNAME
records, one for each App, and one A record for each server (5 Cname
records + 10 A records one for each Webserver= 15 records right?).


Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A
records for each web server. (more 50 A records. in total he will have
50+50=100 A records) Right?
According to mine solution he only needs to map 5 different CNAME records
to the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe), clustering,
Nlb,etc.
But I'm only try to explain how CNAME could be a better work Methodology
( I think).

Please post if you don't agree with that, state your reasons. Just
remember we're talking about Round and Robin solutions, Not Clustering or
any other.

--
Best Regards
Systems Administrator
MCSA + Exchange

Hi Herb that's what I said in previous post (Create two A records with
the same name and different IpAddress, then map CNAME for one that A
records, has the A records have the same name the Round and Robin will
work, right?)
Did you read ?

He needs Round and robin for two different servers....

--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
Thanks. But I am have a doubt could you pls clarify me. Since I
am a beginner I am having the problem to implement that. Could you
pls say me how should I asssign the CNAME and how to set the
properties.
Regards,


Ok I wil try and mail you after i get my result..
Thanks & Regards

CNAMES are NOT used for load balancing, i.e., Round Robin.

CNAMEs would give you multiple NAMES for a single
computer name.

You need A records for Round Robin: Multiple ADDRESSES
for the SAME name.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Hi
Right click in the Domain folder (Under Dns Forward LookUp Zones) and
choose new -> Alias (CNAME).

For example:
You have a domain named: Domain.com, right click the domain name and
choose new Alias, then in the first textbox write App, then choose
the target host, as I aready mention you shoul coose one of the 2 A
records created (AppServer.domain.com)

For more inf check:
How To Configure DNS Records for Your Web Site in Windows Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;324260


--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
Thanks. But I am have a doubt could you pls clarify me. Since I
am a beginner I am having the problem to implement that. Could you
pls say me how should I asssign the CNAME and how to set the
properties.
Regards,

Hi

- Create two A records with the same name and different IpAddress
(Example: AppServer.domain.com-192.168.0.1,
AppServer.domain.com-192.168.0.2)

- Create a CNAME (Canonical Name) that points to the A record
(AppServer.domain.com), note you only need to add the alias name,
for example: your domain is domain.com, and the app is refered by
App, then your alias should be App, it stays (App.domain.com)

- To enable round and robin, right click dns server choose
properties, advanced tab and choose enable round and robin.

That should do the job.




--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
I am deploying my ASP.Net web application in two different servers
I want to
apply or configure those server with load balancing technique (i.e
Round
Robin DNS)

 

[Herb Martin]

I t seems that you don't understand the Admin impact in the scenario that

i gave as example.

I am NOT arguing with you -- and haven't been.

I am stating what MUCH be true about load balancing
with Round Robin and emphasizing that CNAMEs are
unrelated to this -- it is a common misunstanding to
believe CNAMEs are related.

If you know that then you don't have a problem (probably).


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

- But notice that the CNAME records have NOTHING to do with load balancing
or Round Robin. Load balancing through round robin is strictly an A record
issue.

If I was assuming that CNAME records had something to do with Roud and
robin, I wouldn't say that we need to create A records right?


- CNAMES have nothing directly to do with load balancing or clustering/NLB
either.

I never said that CNAME records had something to do with clustering/NLB.


- CNAME records may be useful in a solution but are irrelevant to the LOAD
BALANCING part as they merely give you multiple names for the same IP
address.

I t seems that you don't understand the Admin impact in the scenario that
i gave as example.

--
Best Regards
Systems Administrator
MCSA + Exchange

According to mine solution he only needs to map 5 different CNAME
records, one for each App, and one A record for each server (5 Cname
records + 10 A records one for each Webserver= 15 records right?).

But notice that the CNAME records have NOTHING to do
with load balancing or Round Robin.

Load balancing through round robin is strictly an A record issue.

Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A
records for each web server. (more 50 A records. in total he will have
50+50=100 A records) Right?
According to mine solution he only needs to map 5 different CNAME
records to the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe), clustering,
Nlb,etc.
But I'm only try to explain how CNAME could be a better work Methodology
( I think).

CNAMES have nothing directly to do with load balancing
or clustering/NLB either.

Please post if you don't agree with that, state your reasons. Just
remember we're talking about Round and Robin solutions, Not Clustering
or any other.

Multiple A records provide load balancing amoung EACH
of the addresses associated with each A record -- since the
DNS rotates the order returned to the client and clients tend
to "pick off the top of the list".

CNAME records MERELY provide alternative names for
some (existing) A record name.

CNAME records may be useful in a solution but are irrelevant
to the LOAD BALANCING part as they merely give you
multiple names for the same IP address.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Let me explain:
Of course if you place 2 A records, that will work to.

My solution was in future growth in mind.

You see if in future Madhan has for example:
5 different web applications mapped to 10 web servers:

According with your solution he will have to have 5 different A records
for each web server. (50 A records in total) Right?

App1.domain.com - > 192.168.0.1
App1.domain.com - > 192.168.0.2
App1.domain.com - > 192.168.0.3
App1.domain.com - > 192.168.0.4
App1.domain.com - > 192.168.0.5
App1.domain.com - > 192.168.0.6
App1.domain.com - > 192.168.0.7
App1.domain.com - > 192.168.0.8
App1.domain.com - > 192.168.0.9
App1.domain.com - > 192.168.0.10

App2.domain.com - > 192.168.0.1
App2.domain.com - > 192.168.0.2
App2.domain.com - > 192.168.0.3
App2.domain.com - > 192.168.0.4
App2.domain.com - > 192.168.0.5
etc , and so on ...

According to mine solution he only needs to map 5 different CNAME
records, one for each App, and one A record for each server (5 Cname
records + 10 A records one for each Webserver= 15 records right?).


Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A
records for each web server. (more 50 A records. in total he will have
50+50=100 A records) Right?
According to mine solution he only needs to map 5 different CNAME
records to the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe), clustering,
Nlb,etc.
But I'm only try to explain how CNAME could be a better work Methodology
( I think).

Please post if you don't agree with that, state your reasons. Just
remember we're talking about Round and Robin solutions, Not Clustering
or any other.

--
Best Regards
Systems Administrator
MCSA + Exchange



Hi Herb that's what I said in previous post (Create two A records with
the same name and different IpAddress, then map CNAME for one that A
records, has the A records have the same name the Round and Robin will
work, right?)
Did you read ?

He needs Round and robin for two different servers....

--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
Thanks. But I am have a doubt could you pls clarify me. Since I
am a beginner I am having the problem to implement that. Could you
pls say me how should I asssign the CNAME and how to set the
properties.
Regards,


Ok I wil try and mail you after i get my result..
Thanks & Regards

CNAMES are NOT used for load balancing, i.e., Round Robin.

CNAMEs would give you multiple NAMES for a single
computer name.

You need A records for Round Robin: Multiple ADDRESSES
for the SAME name.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Hi
Right click in the Domain folder (Under Dns Forward LookUp Zones)
and choose new -> Alias (CNAME).

For example:
You have a domain named: Domain.com, right click the domain name and
choose new Alias, then in the first textbox write App, then choose
the target host, as I aready mention you shoul coose one of the 2 A
records created (AppServer.domain.com)

For more inf check:
How To Configure DNS Records for Your Web Site in Windows Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;324260


--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
Thanks. But I am have a doubt could you pls clarify me. Since I
am a beginner I am having the problem to implement that. Could you
pls say me how should I asssign the CNAME and how to set the
properties.
Regards,

Hi

- Create two A records with the same name and different IpAddress
(Example: AppServer.domain.com-192.168.0.1,
AppServer.domain.com-192.168.0.2)

- Create a CNAME (Canonical Name) that points to the A record
(AppServer.domain.com), note you only need to add the alias name,
for example: your domain is domain.com, and the app is refered by
App, then your alias should be App, it stays (App.domain.com)

- To enable round and robin, right click dns server choose
properties, advanced tab and choose enable round and robin.

That should do the job.




--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
I am deploying my ASP.Net web application in two different
servers I want to
apply or configure those server with load balancing technique
(i.e Round
Robin DNS)

 

[Jmnts]

No prob Herb.

--
Best Regards
Systems Administrator
MCSA + Exchange

I t seems that you don't understand the Admin impact in the scenario that
i gave as example.

I am NOT arguing with you -- and haven't been.

I am stating what MUCH be true about load balancing
with Round Robin and emphasizing that CNAMEs are
unrelated to this -- it is a common misunstanding to
believe CNAMEs are related.

If you know that then you don't have a problem (probably).


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

- But notice that the CNAME records have NOTHING to do with load
balancing or Round Robin. Load balancing through round robin is strictly
an A record issue.

If I was assuming that CNAME records had something to do with Roud and
robin, I wouldn't say that we need to create A records right?


- CNAMES have nothing directly to do with load balancing or
clustering/NLB either.

I never said that CNAME records had something to do with clustering/NLB.


- CNAME records may be useful in a solution but are irrelevant to the
LOAD BALANCING part as they merely give you multiple names for the same
IP address.

I t seems that you don't understand the Admin impact in the scenario that
i gave as example.

--
Best Regards
Systems Administrator
MCSA + Exchange

According to mine solution he only needs to map 5 different CNAME
records, one for each App, and one A record for each server (5 Cname
records + 10 A records one for each Webserver= 15 records right?).

But notice that the CNAME records have NOTHING to do
with load balancing or Round Robin.

Load balancing through round robin is strictly an A record issue.

Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A
records for each web server. (more 50 A records. in total he will have
50+50=100 A records) Right?
According to mine solution he only needs to map 5 different CNAME
records to the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe),
clustering, Nlb,etc.
But I'm only try to explain how CNAME could be a better work
Methodology ( I think).

CNAMES have nothing directly to do with load balancing
or clustering/NLB either.


Please post if you don't agree with that, state your reasons. Just
remember we're talking about Round and Robin solutions, Not Clustering
or any other.

Multiple A records provide load balancing amoung EACH
of the addresses associated with each A record -- since the
DNS rotates the order returned to the client and clients tend
to "pick off the top of the list".

CNAME records MERELY provide alternative names for
some (existing) A record name.

CNAME records may be useful in a solution but are irrelevant
to the LOAD BALANCING part as they merely give you
multiple names for the same IP address.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Let me explain:
Of course if you place 2 A records, that will work to.

My solution was in future growth in mind.

You see if in future Madhan has for example:
5 different web applications mapped to 10 web servers:

According with your solution he will have to have 5 different A records
for each web server. (50 A records in total) Right?

App1.domain.com - > 192.168.0.1
App1.domain.com - > 192.168.0.2
App1.domain.com - > 192.168.0.3
App1.domain.com - > 192.168.0.4
App1.domain.com - > 192.168.0.5
App1.domain.com - > 192.168.0.6
App1.domain.com - > 192.168.0.7
App1.domain.com - > 192.168.0.8
App1.domain.com - > 192.168.0.9
App1.domain.com - > 192.168.0.10

App2.domain.com - > 192.168.0.1
App2.domain.com - > 192.168.0.2
App2.domain.com - > 192.168.0.3
App2.domain.com - > 192.168.0.4
App2.domain.com - > 192.168.0.5
etc , and so on ...

According to mine solution he only needs to map 5 different CNAME
records, one for each App, and one A record for each server (5 Cname
records + 10 A records one for each Webserver= 15 records right?).


Now if if tries to add more 5 Apps to this scenario:
According with your solution he will have to have more 5 different A
records for each web server. (more 50 A records. in total he will have
50+50=100 A records) Right?
According to mine solution he only needs to map 5 different CNAME
records to the existent A records. (15+5=20 Records in total) Right?


Of course we have better Solutions for so many Apps (ehehe),
clustering, Nlb,etc.
But I'm only try to explain how CNAME could be a better work
Methodology ( I think).

Please post if you don't agree with that, state your reasons. Just
remember we're talking about Round and Robin solutions, Not Clustering
or any other.

--
Best Regards
Systems Administrator
MCSA + Exchange



Hi Herb that's what I said in previous post (Create two A records
with the same name and different IpAddress, then map CNAME for one
that A records, has the A records have the same name the Round and
Robin will work, right?)
Did you read ?

He needs Round and robin for two different servers....

--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
Thanks. But I am have a doubt could you pls clarify me. Since I
am a beginner I am having the problem to implement that. Could you
pls say me how should I asssign the CNAME and how to set the
properties.
Regards,


Ok I wil try and mail you after i get my result..
Thanks & Regards

CNAMES are NOT used for load balancing, i.e., Round Robin.

CNAMEs would give you multiple NAMES for a single
computer name.

You need A records for Round Robin: Multiple ADDRESSES
for the SAME name.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Hi
Right click in the Domain folder (Under Dns Forward LookUp Zones)
and choose new -> Alias (CNAME).

For example:
You have a domain named: Domain.com, right click the domain name
and choose new Alias, then in the first textbox write App, then
choose the target host, as I aready mention you shoul coose one of
the 2 A records created (AppServer.domain.com)

For more inf check:
How To Configure DNS Records for Your Web Site in Windows Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;324260


--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
Thanks. But I am have a doubt could you pls clarify me. Since I
am a beginner I am having the problem to implement that. Could you
pls say me how should I asssign the CNAME and how to set the
properties.
Regards,

Hi

- Create two A records with the same name and different IpAddress
(Example: AppServer.domain.com-192.168.0.1,
AppServer.domain.com-192.168.0.2)

- Create a CNAME (Canonical Name) that points to the A record
(AppServer.domain.com), note you only need to add the alias name,
for example: your domain is domain.com, and the app is refered by
App, then your alias should be App, it stays (App.domain.com)

- To enable round and robin, right click dns server choose
properties, advanced tab and choose enable round and robin.

That should do the job.




--
Best Regards
Systems Administrator
MCSA + Exchange



Hi
I am deploying my ASP.Net web application in two different
servers I want to
apply or configure those server with load balancing technique
(i.e Round
Robin DNS)