AD Integrated Zones not updating without a reload RRS feed

  • Question

  • I've just noticed something odd with my AD integrated Forward Lookup Zone.  I added a cname entry on one domain controller and a day later it had not been added to any of my other domain controllers.  It would on resolve on nslookup and ping on the server that I added the DNS entry on but none of my other Domain Controllers. I was able to get the entry to show up in DNS on the domain controllers if I reloaded the zone either through the reload on the GUI or running dnscmd server /ZoneReload zonename.  As a temporary fix I've written a script that will run the dnscmd zone reload on all of my domain controllers however I want to figure out why the zone on the DCs are not updating automatically.  Any ideas?
    Friday, May 26, 2017 1:27 PM


  • I think I figured out the issue.  We use OpenDNS on our workstations and servers.  Someone went into the domain controllers and set the primary DNS entry to the OpenDNS appliance.  I've set as the primary DNS entry on all the Domain Controllers.  
    Tuesday, May 30, 2017 1:15 PM

All replies