Ã?Â
Ok, so I have a DNS server that is also running AD. I changed the ip schema from 192.168.0.x to 10.0.100.x. Everything appeared to go perfectly, but after an hour, users were unable to connect to the server. I went into the forward lookup zones and changed the name servers in the properties, and it all updated and worked fine again. 10 minutes later, it is gone again. It keeps going back to the 192.168.0.20 address in the domain.local forward lookup zone, but the _msdts zone remains correctly updated.
Ã?Â
I have rebooted, run the nslookup and it came back as internet address = 192.168.0.20. Rand dcdiag /fix and here is what it puts out:
� � Testing server: Default-First-Site-Name\SERVERAUS� � � � � Starting test: Connectivity� � � � � � � � Although the Guid DNS name� � � � � � � � (da65888b-a7e2-40af-ba0a-4be87e9e7e8a._msdcs.XXXXXXX.com) resolved� � � � � � � � to the IP address (19 ...
Go to the complete details ...