Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Server 2008 R2 DNS and DHCP server (same server).

For some reason over the last few months I've noticed that many of my DNS entries are incorrect. I'll try to remote into a computer via hostname, and I end up at a different workstation than I intended. The only way to remotely find the correct IP is to check the hostname in DHCP and then update the DNS record to correct it.

Is there something I can do to fix this issue with my DNS without having to update each DNS entry manually? Even if I did that I think that this issue would continue to present itself.

share|improve this question
up vote 2 down vote accepted

You are likely having an issue with stale records that haven't been removed. Take a look into enabling Scavenging on your DNS zones, if you are utilizing dynamic DNS updates from your clients. Scavenging examines the records and will remove records that have not been updated in the specified time range. Here is some info on Scavenging Settings and how to enable it:

Enable Scavenging

DNS Aging and Scavenging

share|improve this answer
My zone is already set to scavenge every 2 days (for both settings). – drpcken Jan 3 '12 at 2:18
Do you see entries that are more than 2 days out of date? – David Schwartz Jan 3 '12 at 7:42
Oh yes definitely. I see entries that are 6 months old. – drpcken Jan 3 '12 at 15:38

As cheekaleak already mentioned, you need to configure and enable Aging and scavenging of stale records.

From your comments it sounds like you have configured the aging properties for the zone, but not enabled it for the server. For the actual scavenging process to take place, you need to enable scavenging on a DNS server that holds the zone, not on the zone itself.

The DNS Server will then perform the scavenging, according to the aging and scavenging properties you have configured on the individual zones.

NOTE: The actual time it takes for stale records to be removed is the sum of the configured aging intervals (+ as long as it takes before the next scavenging occurs), so if you have a no-refresh interval of 2 days, a refresh interval of 2 days, and scheduled scavenging to occur every 2 days, you might have to wait for up to as long as 6 days from the record is updated/created and possibly invalidated

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.