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

I'm interning at a company, and it seems like the DNS is really screwed up. There are a bunch of cases where multiple IP addresses are assigned to the same machine in the reverse lookup zone section, and multiple machines are assigned to the same IP in the forward lookup zone section. Is this normal? I feel like it's really messed up and should be fixed. If anyone has any suggestions on how to fix this, please let me know, any help would be appreciated.

share|improve this question

Have you made sure that DNS scavenging is turned on? It'll process the records and delete the old ones on a regular schedule.

share|improve this answer
+1 You got me on the scavenging bit :) – squillman Oct 22 '09 at 19:53
It's enabled in the forward lookup zone but not the reverse, so should I enable it for the reverse lookup zone and change the intervals for the forward lookup zone? Right now, the no-refresh interval and the refresh interval for the forward lookup zone are both 7 days. – shawn Oct 22 '09 at 20:15
7 days is the default. And you do want to scavange both forward and reverse lookup domains. – sysadmin1138 Oct 22 '09 at 20:28

Are these client machine records that are being autocreated? If so check that DNS scavenging is enabled.

Multiple machine names in the reverse zone can be perfectly normal in an environment where machines with multiple IP addresses exist. I'd question that for client/workstation addresses, though.

It's not uncommon to see multiple host records for the same IP in the forward lookup zone. Aliases (CNAMEs) should be used instead, though. Again, this is not typical for client/workstation addresses.

share|improve this answer

This is perfectly normal for servers, especially ones that are doing several jobs such as hosting several websites, one per address.

share|improve this answer
The problem is that it's the workstations that have all these multiple records in DNS, not the servers – shawn Oct 23 '09 at 14:23
Sounds like it might be the legacy of a change in ISP and rather than renumber workstations, they just added new IP addresses and left the old ones in place too? – Michael Dillon Oct 23 '09 at 21:22

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.