Solved

Load Balancing DC's

Posted on 2009-05-12
5
192 Views
Last Modified: 2012-05-06
hi AD guys,

A little while ago, I raised a questions about applications needed a domain controller to point to for LDAP purposes..

http://www.experts-exchange.com/Software/Server_Software/File_Servers/Active_Directory/Q_24382147.html

The solution seemed to be to create a DNS entry named ldap.kam.com and have the applications point to there.

However, I just thought of something...

If I ping kam.com (my domain name) then I am returned the address of a DC.

Instead of creating a DNS entry named ldap.kam.com and pointing to my DC's, do I have this already in the form of "domain.com"?

Was just wondering.
0
Comment
Question by:kam_uk
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 71

Accepted Solution

by:
Chris Dent earned 250 total points
ID: 24369848

Yep you do already have it.

The only reason to use a specific name is if you want to reduce the number of DCs that respond. You should see that domain.com resolves to the IP addresses for all of your DCs (across all sites).

Chris
0
 
LVL 3

Author Comment

by:kam_uk
ID: 24369886
Thanks Chris...and just to confirm, it is strictly round robin only - the closest DC is not taken into account.

For instance, if I am in the UK and have 5 DC's in UK, Germany, US, Japan and Australia (all in the same domain for the sake of argument)..if I used the domain.com name, it would randomly come back with *any* of those DC's?
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 24369920

Yep, correct :)

It rotates the order unless NetMask Ordering gets a chance to come into play.

That would happen if a DC had this IP:

192.168.1.1  255.255.255.0

And the system performing the query had this one:

192.168.1.5  255.255.255.0

It's very limited, if it's not in the same range you don't get a matched response, just standard Round Robin.

Chris
0
 
LVL 3

Author Comment

by:kam_uk
ID: 24372652
Thanks Chris.

Out of interest, how does it "rotate the order"...is that per connecting client, or per per clients....so..let's say I have 10 clients.

Client1 attempts a connection to domain.com and gets the DC at 192.168.1.10
Client2 attempts a connection to domain.com - would it get 192.168.1.10 or another one

or is it

Client1 attempts a conncetionand gets 192.168.1.10
Client1 attempts -another- connection and gets another DC
Client2 attempts a connection and gets 192.168.1.10

Hope that makes sense
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 24372752

It's a global rotation, memorising order per client would be a lot of work :)

No matter the order, if NetMask Ordering can play it will promote any "close" entries to the top of the list.

You can see it in action using a made up record and NsLookup.

Imagine you had a client on the IP 10.0.0.50. And that you had this record set configured in DNS:

host IN A 10.0.0.1
host IN A 10.0.0.2
host IN A 10.40.0.1
host IN A 10.40.0.2
host IN A 172.16.1.1

While you're in the same classful subnet as some of those records (NetMask Ordering defaults to 24 bit subnets, but can be changed to other Classful subnets, 8 bit and 16 bit). You will find that this response order is used when repeatedly queried:

10.0.0.1, 10.0.0.2, 10.40.0.1, 10.40.0.2, 172.16.1.1
10.0.0.2, 10.0.0.1, 10.40.0.2, 172.16.1.1, 10.40.0.1
10.0.0.1, 10.0.0.2, 172.16.1.1, 10.40.0.1, 10.40.0.2

Go a bit slow (a second or two between each query), because it won't rotate the order exceptionally quickly. More likely down to NsLookup behaviour than anything else.

If there was only one record in the same subnet as the client it would always respond with that address. e.g.

10.0.0.1, 10.40.0.1, 10.40.0.2, 172.16.1.1
10.0.0.1, 10.40.0.2, 172.16.1.1, 10.40.0.1
10.0.0.1, 172.16.1.1, 10.40.0.1, 10.40.0.2

If you were to query that set of records from a different machine, one that isn't on any matching range you'd get this behaviour:

10.0.0.1, 10.40.0.1, 10.40.0.2, 172.16.1.1
10.40.0.1, 10.40.0.2, 172.16.1.1, 10.0.0.1
10.40.0.2, 172.16.1.1, 10.0.0.1, 10.40.0.1

Chris
0

Featured Post

Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question