So I have a domain controller (windows 2012 server) that has been moved to a new location. It had to have the IP address changed to match the new network. SO now that this has all happened it appears to have fouled up all my dns setting because I cannot join computers to the domain. The client computers that are trying to join are using the IP address of the DC as the primary DNS. I know its something with the dns settings (lookup zones) on the server im just not sure what I dont have configured right. the new dc controller IP is 10.0.0.90 and I have removed all the old entries in DNS and added new zones pointing to the new address. Is there a simple way to rebuild this?
Now, check the workstation:
1. Check the HOSTS file
2. Check the LMHOSTS file
3. Check the DNS settings on the workstation. They should ONLY point to the server's CURRENT private IP. There should not be any other DNS servers listed (no ISP DNS servers, no google servers, nothing... JUST the DC).
4. IDEALLY, post screen shots of all of the above.
Now check the server:
1. Does the server's TCP/IP properties DNS listing ONLY point to itself (I prefer by server IP and NOT the loopback address, though that should theoretically be fine)?
2. Restart the netlogon service on the server. That should re-register all AD records in DNS.
Are things working now?
No? Try joining the fully qualified domain name instead of the netbios name.
No? Try adding the dns suffix to the system properties of the domain name.
No? Post screen shots of the server.