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?




xmouserAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Toni UranjekConsultant/TrainerCommented:
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
0
xmouserAuthor Commented:
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.
0
Toni UranjekConsultant/TrainerCommented:
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.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

xmouserAuthor Commented:
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.
0
Toni UranjekConsultant/TrainerCommented:
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.
0
xmouserAuthor Commented:
OK, trying that tomorrow.
0
xmouserAuthor Commented:
Why the response from different names for the same IP?
0
Toni UranjekConsultant/TrainerCommented:
BTW, how is your No-refresh interval configured and if you use DHCP, how is lease duration configured?
0
Toni UranjekConsultant/TrainerCommented:
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.
0
xmouserAuthor Commented:
And why - I'm going to get asked.  Something is responding to the ping request.  I can't imagine that it is the server
0
Toni UranjekConsultant/TrainerCommented:
It's not server, that it is responding. Are your servers configured as DHCP clients? It's usualy one of DHCP clients. Try pinging the IP address with -a switch to find correct name. Delete other records.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.