finding incorrect Sites listings in DNS that do not correspond to ADSS

DaleatEMS-0938 0 Reputation points
2024-06-27T18:31:45.0266667+00:00

Within an enterprise that has an aged Active Directory domain structure of multiple decades in age and AD Integrated DNS (replication tested as healthy ...dcdiag) ...as a somewhat new admin have found that changes I've made to update ADSS are not reflected in DNS. Instead there is outdated Sites information found under the Forward Lookup Zones ... _MSDCS.dom.tld->DC->Sites, _MSDCS.dom.tld->GC->Sites, and dom.tld->_sites

What I've done is use dcdiag to perform tests that show healthy replication and no errors, examined the Event Logs on the FSMO holder DC (holds all the roles - there are two other DC's ...one at primary site ...one at colo site), have used NTDSUTIL to examine domain metadata and ensure that no improperly demoted former DC's are listed in the two sites that contain DC's

Perhaps this isn't causing any issues - but why is this "sites" information out of sync with ADSS? Can it be corrected and if so how?

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,235 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Jing Zhou 5,210 Reputation points Microsoft Vendor
    2024-07-01T09:32:59.1733333+00:00

    Hello,

     

    Thank you for posting in Q&A forum. To further troubleshoot this issue, please kindly try: 1.Open CMD window and try to ping domain name to check the connectivity between issued server and domain. 2.Run CMD command ipconfig /flushdns ipcofnig /registerdns and check it again. 3.Run repadmin/syncall command On the DC and check if the DNS record is synced or not.

     

    Best regards, Jill Zhou

     

    If the Answer is helpful, please click "Accept Answer" and upvote it.