Host (A) records vanishing from DNS server

Hi

Last night I installed some Windows Updates and rebooted all of our servers.

Shortly afterwards I noticed that I couldn't ping some of our servers.

I noticed that the Host (A) records in the Forward Lookup Zones for these servers had vanished. Once I did an ipconfiig/registerdns on the member servers the records recreated successfully.

Why would the records vanish? We do not have scavenging enabled.

Recently we installed two new DCs in to our domain, which are both DNS servers (AD integrated). These are both Windows Server 2008 machines. We have an existing 2003 DC with DNS, and changed all the member servers to point to the new 2008 DCs for their DNS. They used to point to the 2003 DC.
failedAsked:
Who is Participating?
 
failedAuthor Commented:
We never got to the bottom of this problem.
We enabled a higher level of logging in case it happens again.
0
 
emadallanCommented:
why did you install 2008 dc? are you intend to upgrade your AD from 2003 to 2008? if so there are more steps need to be accomplished to upgrade to 2008?
0
 
failedAuthor Commented:
Yes we are upgrading to a 2008 domain.
0
WEBINAR: 10 Easy Ways to Lose a Password

Join us on June 27th at 8 am PDT to learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees. We'll cover the importance of multi-factor authentication and how these solutions can better protect your business!

 
Chris DentPowerShell DeveloperCommented:
It's most common to see records randomly disappear when Aging settings are too low. That is, if the Refresh interval is anything less than 24 hours we see things start to fall apart.

Do you have aging / scavenging configured?

Chris
0
 
failedAuthor Commented:
As I said in the question, we do not have ageing/scavenging enabled.
0
 
Chris DentPowerShell DeveloperCommented:
Apologies, thought I read that through a bit more carefully.

Other options are:

1. Administrative action (aka user error), which I imagine you accounted for.
2. Zone corruption. Harder to test, although sometimes you can see enough by checking through the zone in AD (tends to exhibit and objects prefixed with CNF in ADSIEdit).

Zone corruption aside, DNS won't be killing records on its own, and we can rule out Dynamic Update. I assume the servers having this trouble are using static IP addresses? If so we can also rule out any action DHCP might take on the zone (if you use DHCP at all / if DHCP is allowed to update DNS).

Chris
0
 
failedAuthor Commented:
Hi Chris-Dent,

The servers are set static IP addresses in the IP settings in the member servers' IP properties. We haven't created static records manually in DNS.

Please could you provide more detail on how to look for zone corruption?

Thanks
0
 
failedAuthor Commented:
Did not get to the bottom of the problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.