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

did a quick sweep of a network this morning and i am getting different hostname to computername in the list.

this is a domain with a DC in there. it has active directory integrated dns.

if you use nslookup to find names there are no issues, but if you do a sweep it has varying computer name to hostname mappings? i have looked under the DC dns forward lookup and things seem fine and no duplicates in there?

can anyone suggest where this issue might come from?

share|improve this question
did you check reverse entries for the subnet that you scanned? – johnh Dec 17 '09 at 16:23
good point, do you mean just looking at the reverse dns lookup zone? – user8256 Dec 17 '09 at 16:27
you are right, the reverse lookup has multiple SAME ip to different hostname? how come? is there a setting i can change or scavenge? thaks – user8256 Dec 17 '09 at 16:29
on the general tab in the properties of the zone, you can adjust the aging and scavenging details. – johnh Dec 17 '09 at 16:36
did that and forced a scavenge of stale records with not much luck any other suggestions? – user8256 Dec 17 '09 at 17:05
up vote 1 down vote accepted

DNS scavenging does not affect manually created DNS records, only dynamic DNS records. You probably want to go in and clean up the reverse lookup zone by hand (assuming that the incorrect records were added manually to the forward lookup zone).

share|improve this answer
actually i think the problem is that there was a second DC in a remote site, the vpn tunnel has stopped working since there was an issue with the server adn it was taken offline in the remote site but never dcpromo demoted. If there are records, which there are, in the Active Directory Sites and Services, is there a best practice to clean up the remote site subnet? I want to remove the old second DC and i guess do a ntdsutil metadata cleanup. Any suggestions? I think that the main DC is trying to replicate the forward and reverse DNS and maybe not scavenging due to it waitiing on the second dc – user8256 Dec 17 '09 at 18:06
the second DC is the one that no longer exists due to the vpn tunnel and the fact that the tech has wiped it and made it just a stand alone server there. – user8256 Dec 17 '09 at 18:07

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.