So here's what I did:
I was changing the IP address of both parent and child DCs to 172.16.7.xx.
1. Create a new subnet in SITES AND SERVICES for 172.16.7.x
2. Create a REVERSE ZONE in *each* DNS (parent and child) for 172.16.7.x
3. Change IP address the NIC in parent DC
1. Be sure to change the DNS server entries in the NIC to use the new
address!
2. REBOOT
4. Change IP address the NIC in child DC
1. Be sure to change the DNS server entries in the NIC to use the
new
address!
2. REBOOT
5. Log into each DC, and look at DNS (wait a few minutes, for things to
replicate and start properly)
1. check the FORWARDERS of the child zone on the child DC. Make sure
they ALL use 172.16.7.x; if not, delete each entry and re-add as the new
172.16.7.x address
2. Check the NAME SERVERS tab of *each* zone on *both* DNS servers.
Make sure they ALL use 172.16.7.x; if not, delete each entry and re-add
as the new 172.16.7.x address
1. parent zone on parent DC
2. child zone entry on the parent DC
3. child zone on child DC
3. Check NAME SERVERS tab of reverse zone
1. Create entries in the reverse zone, if necessary.
Once I did all that, life was good. I could do forward and reverse
NSLOOKUPs of both DCs, from both DCs. And DCDIAG wasn't complaining
about DNS (outside of the fact that the parent DC has no forwarders, as
it is isolated from the outside world, as a lab environment).
Was easier than I thought it would be. The key was that reboot (it might
have worked if all I had done was restart the DNS server after changing
the address, but simple enough to reboot). AND (in my case) to wait a
couple minutes after booting.
Thanks to everyone that helped! Couldn't have done it without you guys.
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin
