Server migration ADDS, DNS etc. now DNS issues?
Hi
I recenlty migrated a 2021 r2 DC and its now been removed as a DC. The replacement seems to be working ok, however i have had some issues with the time service which seems to have been on the old server.
Clients were getting the wrong time which has been causing no end of issues.
I now have the following problems:
Remote desktop services - will not load using the hostname. the ip works as a workaround.
Printing - a number of machines at a remote site cannot print. they can ping the printer.
Local CRM - name.domainname.co.uk isnt loading and is actually loading the domainname.co.uk (our website) rather than the local application thats on the server.
I'm leaning towards DNS not working properly.
How can i check?
Thanks
PS - have changed the primary NTP server to the RID master using this link https://community.spiceworks.com/how_to/65413-configure-dc-to-synchronize-time-with-external-ntp-server
I would check and make sure none of the other DC's still reference the old domain controller for their DNS and that where the old DC's IP exist was replaced with the new one.
You should also check your DHCP options. Your clients could still be getting the IP address of the old DC if the DHCP options were not modified to the new DC.
ASKER
Yes DCs and member servers all look correct now.
I changed the dhcp scope after removing the main DC external NTP server to use time servers in dhcp.
Still have the same issues.
ASKER
Reboot of the new DC resolved most issues.
Turned off the old one also - still had its IP but no services running.
Step 1: Let's start with setting up time: Set up PDCe NTP Domain Time in a Virtualized Setting
Step 2: NewDC DNS0 points to SELF with others BLANK
Step 3: DNS Forwarders set up for OpenDNS or other of your choice
Please post an IPConfig /ALL into a CODE Snippet and sanitize as needed.
ASKER
So I've setup the PDCe as the NTP server using the commands I see on your post (as close as) and the other clients and member servers took a few minutes to update.
There were also old DNS IPs in the network settings of some servers.
I also added time service to the DHCP scopes.
The remote site had a cisco router acting as dhcp server and the DNS IPs were all wrong (4x) and the last server i removed was the only one working at that time.
We are using Open DNS and the DCs are using these.
So now we have a NTP server at one site for all 3 sites. All members and client, phones are talking to this. We are also pointing our VMWare hosts and applainces to 4x dcs.
All looks good now.
Should we have multiple NTP servers as a colleague says?
ASKER
No i meant configure more than 1 DC with external pool/NTP servers, not more NTP server on the single DC.
The PDCe is the _only_ time authority in the Forest/Domain. All other DCs will _represent_ the PDCe but that's it. They will answer an NTP request but there can only be one time authority.
EDIT: That's represented in my blog post linked above.
ASKER
Time wise all is workign now. Changing the old server to the new one and forcing this external NTP as per your reg entries.