munozm
asked on
Configuring Clients/Servers for Active Directory Integrated DNS
Is there a way I can direct network clients and servers to Active Directory DNS without hardcoding an IP address? If I have multiple Domain Controllers that are also DNS servers, can the client be configured to use the DC that validated them when logging on to the domain (a.k.a. LOGONSERVER)? I'm upgrading our Forest & Domain from 2000 (yes, I know) to 2003 and then 2008 and I don't want to have to change all the servers and DHCP servers more than once. If I had to, can I reassign the IP address of the current DNS server to a DC? Will AD, GC, DNS, etc get upset if I change the IP address of a Domain Controller?
Thanks...
Thanks...
Reassigning the DNS server IP will work
Is it possible to leave behind one DNS and just use that till you are done upgrading? Then change the dhcp to point to the new 2008 dns servers?
ASKER
I expect that both suggestions would work, but I was hoping that if every DC is a DNS server, what's the point if clients aren't going to access them? Sure, it's an online backup, but how often do you lose a DNS server...especially in a VMware environment?
You define them in order to ensure preference is kept i.e. to closest DNS servers - you can go into advanced options for the adapters and assign more than the default 2
ASKER
This is all true, and I appreciate the responses.
I was thinking that if AD authenticates a user by directing them to a DC in their site by subnets or the first DC to respond, I was hoping that DNS will act the same way and there wouldn't be a need for hardcoding IP addresses
I was thinking that if AD authenticates a user by directing them to a DC in their site by subnets or the first DC to respond, I was hoping that DNS will act the same way and there wouldn't be a need for hardcoding IP addresses
Hello,
depending on how you wish to configure the DHCP you can have scope for each site and then configure the primary DNS and secondary DNS server IP in each scope as per your preference.
This is the best approach to what you wish to achieve.
depending on how you wish to configure the DHCP you can have scope for each site and then configure the primary DNS and secondary DNS server IP in each scope as per your preference.
This is the best approach to what you wish to achieve.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Trying to close
ASKER
Contacted Microsoft and they confirmed this cannot be done