Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.
Question about creating a DNS load balance between domain controllers
Hi,
A small background before my question :) -
I had a need to create a load balance service name between all the domain controllers, i know i could use the default domain name instead, but it had connections to other servers except for the domain controllers.
So....
since i can't create the same multiple dns host to multiple servers i created a new subdomain and had all the domain controller's IP name SAME AS PARENT...so all would get the same DNS name of the new subdomain, hence creating a DNS Load Balance.
Here's my question though, how does it work? is it round robin? who answers first? the dc the computer is connected to or the DNS the computer is connected to?
AND the most important factor what if one of the domain controllers isn't available, will the be a timeout? or will the query never reach it in the first place?
A small background before my question :) -
I had a need to create a load balance service name between all the domain controllers, i know i could use the default domain name instead, but it had connections to other servers except for the domain controllers.
So....
since i can't create the same multiple dns host to multiple servers i created a new subdomain and had all the domain controller's IP name SAME AS PARENT...so all would get the same DNS name of the new subdomain, hence creating a DNS Load Balance.
Here's my question though, how does it work? is it round robin? who answers first? the dc the computer is connected to or the DNS the computer is connected to?
AND the most important factor what if one of the domain controllers isn't available, will the be a timeout? or will the query never reach it in the first place?
Asked:
-
4
2
1 Solution
LVL 37
If all your DC's are running DNS then all you need to do is list all of he DC's IP addresses in the NIC cards DNS settings on all machines. Windows will take care of the rest. No need for ANY load balancing, round robbins or square ones.
I didn't understand how this will create a load balance?
my need is to ping a name for example (dns.company.com) and have a redundancy (perhaps i should have used that therm instead of the load balance since it explains my needs better) between all domain controllers.
my need is to ping a name for example (dns.company.com) and have a redundancy (perhaps i should have used that therm instead of the load balance since it explains my needs better) between all domain controllers.
I have several applications that connect to Active Directory using LDAP directly to a Domain controller server, i don't want to give them the name of 1 domain controller since if it's down then the service is down, so....i want to create a DNS alias name to hold behind it all available DC's
I'll get the easy part out of the way first:
To answer the question, there's no true load-balancing mechanism built into DNS. Round-robin DNS does load balancing only on the most basic level; it doesn't care whether a given server is down and will return its IP address anyway. Network Load Balancing (NLB) is outage-aware, but I can't think of a way to make it work in this scenario. If those apps that you're running are AD-aware, they should be able to use AD's built-in mechanisms to locate a DC that's running. Have you actually experienced problems with them?
Here's my question though, how does it work? is it round robin? who answers first? the dc the computer is connected to or the DNS the computer is connected to?Yes, it's round-robin by default. You can disable round-robin in the properties pages of the DNS servers (under the Advanced tab, I believe), but there's typically no reason to do this. So the first time a DNS server is queried for that name, it'll return the IP address of the first corresponding host record. The second time it's queried, it'll return the second one, etc. It should be mentioned that you won't see this exact behavior on a client. Multiple queries for the same name from a single client will return the same IP address for a while, because the client will have that address in its resolver cache and won't actually query a DNS server until the cached record expires or the entire cache is flushed.
i know i could use the default domain name instead, but it had connections to other servers except for the domain controllers.Are you saying you've got blank host records in DNS (host records with the name "same as parent folder") referring to machines other than domain controllers? If so, that's a problem. Those records are used by domain members to locate a DC, and they shouldn't ever refer to anything but DCs.
To answer the question, there's no true load-balancing mechanism built into DNS. Round-robin DNS does load balancing only on the most basic level; it doesn't care whether a given server is down and will return its IP address anyway. Network Load Balancing (NLB) is outage-aware, but I can't think of a way to make it work in this scenario. If those apps that you're running are AD-aware, they should be able to use AD's built-in mechanisms to locate a DC that's running. Have you actually experienced problems with them?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now