To take a step back, my test environment is one DC and one member server (to
be the control station). I want to rename my test domain TEST.COM (TEST for
NetBIOS) to ABC.COM (ABC for NetBIOS). As I stated before, I have run
through the Step-by-Step Guide multiple times and successfully change the
NetBIOS name to ABC. The process also changes the DNS and domain setting on
the member server such that, after the requisite reboots, I can log into the
ABC domain and verify that the server's primary DNS suffix is ABC.COM.
When I turn my attention to the DC, I successfully change its primary DNS
suffix to ABC.COM and reboot. Getting back to my real question, after all
systems reboot, I bring up a command prompt and, from the DC, ping the member
server (STANDALONE.ABC.COM) with only the name STANDALONE and it resolves to
STANDALONE.TEMP.COM with a successful ping. When I ping STANDALONE.ABC.COM
the ping can not resolve the name. I try the same ping from the member
server to the DC and receive the same results. If I go into the DNS MMC,
there is no ABC.COM entry, but there is an entry for TEMP.COM.
Did I miss something? Or is there a method for me to create an ABC.COM zone
in the DNS MMC? Are there any tie-ins into the AD?
Thanks,
Jeff
Are you using integrated DNS or not?
--
With best regards
Nickolay Domukhovsky, MCSA
I suppose I can modify the zone in the DNS MMC such that it is not AD
integrated then manually change from the TEMP.COM to the ABC.COM DNS domain,
but I'm still worried about any "hooks" that might exist from the initial
DCPROMO process that tied the Windows domain to the DNS domain
What you can do know...
Create DNS zone ABC.COM (integrated, if you are using this one) in DNS
MMC, allow dynamic updates to this zone.
Then run netdiag /fix /test:DNS on your DC (you need Support Tools
installed).
Also you can run ipconfig /registerdns on each domain member (or simply
wait a while).
TEMP.COM zone you can simply delete - you have no use for it now, since
you are ended rename process.
Jeff