[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 415
  • Last Modified:

Enabled DNS scavenging and now 3 of my 5 reverse DNS zones were mostly deleted.

I enabled DNS scavenging and now three of the five reverse DNS zones had most of the clients removed. I am not sure why the other two are OK. They just had old records removed but the other three had pretty much everything removed. Why did this happen? How can I make sure reverse DNS is going to update correctly from now on? This is for 2008 windows server DNS integrated zones.

Thanks,


Justin
0
JustinGSEIWI
Asked:
JustinGSEIWI
  • 3
  • 2
2 Solutions
 
Santosh GuptaCommented:
Hi,


lets enable the Tracking of DNS Record Deletion and see how and why records are getting deleted.

http://blogs.technet.com/b/networking/archive/2011/08/17/tracking-dns-record-deletion.aspx

Also check the below options.

dsn
0
 
JustinGSEIWIAuthor Commented:
I enabled the recommended setting on my scavenging DNS server. The settings are the same as your picture above except I changed it "always dynamically update." Should I do this on all five of my DNS servers? I am thinking I will need to, especially the ones that have mostly empty reverse DNS zones at the moment.

Someone else told me to wait because DHCP clients only update reverse DNS every 24 hours or so. Do you agree with this?

Also, the records disappeared after I told the server to scavenge DNS records. The event log below was logged when this happened.

Event Type:      Information
Event Source:      DNS
Event Category:      None
Event ID:      2501
Date:            4/9/2014
Time:            2:46:57 PM
User:            N/A
Computer:      DC01.ad.gs.org
Description:
The DNS server has completed a scavenging cycle:
Visited Zones     = 9,
Visited Nodes     = 693,
Scavenged Nodes   = 259,
Scavenged Records = 264.
 
This cycle took 1 seconds.
 
The next scavenging cycle is scheduled to run in 168 hours.
 
The event data will contain the error code if there was an error during the scavenging cycle.



I am thinking the "always dynamically update" setting will eventually fix this if I give it a couple of days. What do you think?

Thank you,

Justin
0
 
footechCommented:
I would definitely give it a few days to let it populate.  If you look in the DNS Management console, you should see the timestamps for all the records being updated.  The records are refreshed depending on your configured refresh and no-refresh intervals.  So once a record is refreshed, you shouldn't see another update to the record until at least the no-refresh interval has passed.  The following link should help you understand how this works.
http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
footechCommented:
I got a notification that an administrative comment was posted in this thread, but there is no comment, and the thread is re-opened.  What's going on?
0
 
footechCommented:
Very well, no objection.
0
 
Santosh GuptaCommented:
Pleased to help you..
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now