Reverse lookup zone in dns is not updating
They represent what servers have the authority or permission to create records. Well, what happens when we delete those delegated subfolders and cycle the DNS Server service? What my customer ended up doing compounded the problem significantly. When they deleted the 50 or so reverse zones from DNS, that’s all they did before trying to restore their original zone from a backup.If you scroll back up and look at the figure that shows the contents of the subfolder, you’ll see a single NS record of the DNS server I used in the lab. No one bothered to look at the subfolders that got created when they built out the additional reverse DNS zones! But that would have required some due diligence and a thorough discovery first before making drastic changes. Don’t let someone outside your org that doesn’t know the environment implement major config changes without knowing exactly what they are getting themselves into…Yes, I’m one who tells it like it is.Next, I’ll simply do what my customer did, and create 3 reverse zones that correspond to the subnets of the static entries I created. Each one only contains an SOA and NS record…and that’s it. Event 4010…The system can’t create a resource record for the missing static entries. Some of you might have come across this little nugget when migrating the _msdcs zone during a domain upgrade…(sound familiar? However, in the situation above they witnessed events 4004, 4013, and 4015.This is the point in the scenario where it became a “mic drop moment” and the IT crew left the building. Oh, they will get populated with PTRs when clients start to re-register up, but until that happens, they’ll remain empty. There they are along with the new zones…but…how come the static entries aren’t in DNS Manager? More often than not, this indicates that the “preferred” or primary DNS server in TCP/IP properties of the NIC on the DNS server (or DC) is pointing to itself.Once it got to the newer zones, as the static records weren’t there…then reverse lookup fails. Feel free to lab it up on your own and test various scenarios.Watch how the simplest action can either save or wreck an environment.(read more here) but this little particular nugget appears to encompass something entirely different.
That said, there are multiple ways various types of records can mysteriously “poof” away, such as duplicate zone creations, misconfigured scavenging settings, etc.During one of my regular DSE visits to my client, I was following up with what occurred that caused a Severity A support case to be opened.While gathering information and details, I was told “We had static reverse DNS records vanish.” I was like…Say what? How in the world do STATIC records just vanish without someone deleting them?! PFE Tim Beasley here coming to you live from the warm, cozy sands of Bora Bora…Pfft yeah. But I digress, I am writing this post to hopefully shed some light on a bizarre issue I recently faced at one of my dedicated (DSE) customer sites. No I’m in Missouri…where it’s miserably winter outside.