Link to home
Start Free TrialLog in
Avatar of xmouser
xmouserFlag for United States of America

asked on

DNS scavenging

Server 2003, Active Directory Integrated.

I have a site with hundreds of entries in DNS; Server name>Forward Lookup Zone>Domain.

There are multiple listings of computers Host (A) records.  These entries are computers that have been taken off the domain, renamed and placed back on the domain.  This has been going on for months.

Example:

123-DFED-4a            10.10.10.34
123-DFEDasw            10.10.10.34
4eed-cdeede            10.10.10.34

Under aging I selected Scavenge stale resource records changed the Refresh interval to 1 day.

Then from the console I right selected the server and chose Scavenge stale resource records.  There was no change.  I waited a few days to see if some automatic maintenance feature would work this out but there wasnt any change.

No significant events in event viewer.

If you ping 123-DFED-4a you get a reply from 10.10.10.34.
If you ping 123-DFEDasw you get a reply from 10.10.10.34.
If you ping 4eed-cdeede you get a reply from 10.10.10.34.

Thoughts?




Avatar of Toni Uranjek
Toni Uranjek
Flag of Slovenia image

Hi!

In DNS console go to View, select Advanced. Right click your zone and on the general tab you should see the follwing field "The zone can be scavenged after", what's the date?
How is no-refresh interval configured?
If you double click any record, what is the time stamp for each record?
What type of zone are we talking about? Standard Primery or AD integrated?

Toni
Avatar of xmouser

ASKER

AD integrated
The new zone scavenge date is the 11th, however earlier in the week when I made the original changes that date has passed.  So I would expect to see something by now.
Did you check when single records can be deleted? There is an issue with scavenging old records if scavenging was disabled on a standard zone and you enabled scavenging, the server will not scavenge records that existed before you enabled scavenging. The server does not scavenge those records even if you convert the zone to an Active Directory-integrated zone first. To enable scavenging of such records, use Dnscmd.exe oa delete them manually.
Avatar of xmouser

ASKER

Hmm interesting.  Why not select them all and delete them?

The zone wasn't converted to AD Integrated recently - 18 months ago?  So I don't think that is the issue.
If records belong to client computers which are not on the network anymore - what's stopping you delete them? Oh, you might delete a record for machine that is still on the network? It will register itself in next couple of days and nobody will miss their records. ;)

This is how I do it - but be carefull, please don't delete any server records.
Avatar of xmouser

ASKER

OK, trying that tomorrow.
Avatar of xmouser

ASKER

Why the response from different names for the same IP?
BTW, how is your No-refresh interval configured and if you use DHCP, how is lease duration configured?
You are actually getting response only from one computer, it just that with your situation your DNS server "thinks" that this computer is named 123-DFED-4a, 123-DFEDasw and 4eed-cdeede at the same time.
Avatar of xmouser

ASKER

And why - I'm going to get asked.  Something is responding to the ping request.  I can't imagine that it is the server
ASKER CERTIFIED SOLUTION
Avatar of Toni Uranjek
Toni Uranjek
Flag of Slovenia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial