Performed a domain rename, however the dns records did not update.

Well all of the warnings on how hard a domain rename can be were correct. I performed a domain rename, the domain has been renamed successfully. However, none of the dns records were created or updated for the new domain. I renamed the domain from somthing-something.com to something.net. As described in the ever so convoluted directions provided by microsoft, prior to doing the rename I create the DNS zones for the something.net domain as well as the SRV record. Luckily I only changed the domain name and the NETBIOS name remained the same, so my users can still get in this morning. But now how do I correct my DNS situation. Everything I have tried to look up simply says that DNS is automatically handled during the DCPROMO, which it is, but doesn't say how to do the DNS configuration manually. Can someone help a brotha out?
LVL 4
jojuezAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
PlaceboC6Connect With a Mentor Commented:
So you might just need to change your primary dns suffix.

Control Panel
System
Computer name
Change
"More" button
This will allow you to change it to the new name.

It'll probably want to restart.
That should register dns records when it boots.
0
 
KCTSCommented:
How long have you waited - DNS may take a little while to catch up.
0
 
jojuezAuthor Commented:
Over night now. I had let it go for about 15 minutes last night before i decided to step away to get a fresh look. It is the only DC on my network as well as the only DNS server.
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
PlaceboC6Commented:
Do an IPCONFIG /ALL on the domain controller.
Check the primary dns suffix and see if it matches the new domain name.

If so, restart the netlogon service and check the system event log for errors related to netlogon.
After restarting the netlogon service,  open the new zone you created for the new domain name and verify whether it is being populated or not.

If the primary dns suffix of the dc doesn't match the new domain name,  that will explain why the server isn't populating the new zone you created.
0
 
KCTSCommented:
Ok it shouldn't take as long as that.
0
 
jojuezAuthor Commented:
After doing the /all it still shows the old domain name in the dns suffix.
0
 
PlaceboC6Commented:
So if you pull up:

Control Panel
System
Computer Name tab
Does it report that your domain membership is the new name?

If so,  then you might just need to change your primary dns suffix and bounce the netlogon service to register the SRV records.

I've never done a domain rename operation before,  so I'm a little sketchy on the final bits where the server assumes its new identity.
0
 
jojuezAuthor Commented:
The full computer name the name still shows as servername.somthing-something.com. The domain shows as something.net
0
 
jojuezAuthor Commented:
I will give that a shot. I will have to wait till the lunch hour to bring the server down though. Will post back after i have tried that.
0
 
PlaceboC6Commented:
Sounds good
0
 
PlaceboC6Commented:
Any news?
0
 
jojuezAuthor Commented:
It looks to be working. I am waiting to see when the last of my traveling sales people get in to make sure they can get on the domain.
0
 
PlaceboC6Commented:
Sweet.  :)
0
 
jojuezAuthor Commented:
Thanks for your help by the way!! Monday everyone should be in office and that will be the real test there.
0
 
PlaceboC6Commented:
Cool.   No problem.  Lemme' know.
0
 
PlaceboC6Commented:
jojuez,   Did you get a chance to test this on Monday?
0
 
jojuezAuthor Commented:
Thank you for all your help. It is up and running now.
0
 
PlaceboC6Commented:
You are welcome.  Have a good one.
0
All Courses

From novice to tech pro — start learning today.