cdavidson0724
asked on
Active Directory integrated DNS zone - client registration process.
I'm in the process of planning for an NT to Active Directory migration for an environment that is approx. 3000 users, 3000 workstations, and 350 servers. I'm working on planning my DNS infrastructure at the moment. Initially we are planning on having 4 domain controllers that will also serve as our AD-integrated DNS servers in the DHCP scope. We will remove the root-hints from these four machines and set them up to forward to a pair of caching DNS servers that will then forward out to our ISP's servers. My question is, when a client machine or member server starts up and registers itself in DNS, will it always try to register with the first DNS server in it's TCP/IP properties/DHCP assignment, or does it pick one of its DNS servers at random? I'm concerned because if this is the case, then that one DNS server/Domain Controller that is first in the DHCP scope will be getting slammed first thing in the morning with all of the authentication requests and DNS registrations that it will be receiving. Any suggestions are appreciated. Thanks in advance.
Bradley Fox
Since you have so many workstations that will be starting up at the same time you should look at creating a DHCP cluster. Configure the DHCP server to do the dynamic updates instead of having the clients do it themselves (much more reliable). I would also install DNS on the DHCP servers, this way they should update the DNS records on themselves then replication will take care of the rest.
ASKER
Good point and I would consider that, but currently our Network Management team runs DHCP from Cisco Network Registrar, so our side of the house has no control over DHCP.
Any ideas on how client machines and servers choose which DNS server to register with?
Any ideas on how client machines and servers choose which DNS server to register with?
I'm pretty sure they are going to hit the first server on the list. And since you are assigning IP addresses via DHCP it's going to be the same server.
I guess since Cisco is handling DHCP your best bet would be to setup a "Server Cluster" for DNS. You will assign a virtual IP to the cluster, make that the first DNS address that's handed out by DHCP.
I guess since Cisco is handling DHCP your best bet would be to setup a "Server Cluster" for DNS. You will assign a virtual IP to the cluster, make that the first DNS address that's handed out by DHCP.
ASKER
Wouldn't that require me to cluster my domain controllers since DNS will live on the same boxes?
You can run DNS on a box that's not a DC.
ASKER
I thought that AD-integrated DNS zones had to live on DCs.
I apologize, you are correct...Integrated DNS zones do have to reside on a DC. You will have to make each of these "cluster dns" servers a DC as well.
ASKER
I'm not entirely sure that you can or would want to cluster a domain controller.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks mvvinod...point taken
You are welcome ! Glad to help.