DNS Not clearing up records

I ran across this issue a few days ago and can't seem to find anything on
Microsoft's site to solve the problem.



Under DNS Management (dsnmgmt) I have noticed that under my .local there
many machines listed under there that are no longer a part of my network. I
have also noticed that some of the machines are listed more than once and
that some even have the same IP address.



I have looked at the DHCP server and it seems to be working fine. I have
addresses set to renew ever hour as I was testing to see what might be
causing the problem.



It just doesn't seem that DNS is cleaning up after itself.



Any help you can provide about this issue is GREATLY appreciated.

As far as I understand you habe a problem with the config of "Aging and
scavening period"

At your DNS server properties first enable the "Set Aging and Scavening ..."
its default perioed to clean old datas 7 days
check it

Good Luck

ILKER SOGUT

"-=M@rk=-" <someone@(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I ran across this issue a few days ago and can't seem to find anything on
>Microsoft's site to solve the problem.
>
>
>
> Under DNS Management (dsnmgmt) I have noticed that under my .local there
> many machines listed under there that are no longer a part of my network.
> I have also noticed that some of the machines are listed more than once
> and that some even have the same IP address.
>
>
>
> I have looked at the DHCP server and it seems to be working fine. I have
> addresses set to renew ever hour as I was testing to see what might be
> causing the problem.
>
>
>
> It just doesn't seem that DNS is cleaning up after itself.
>
>
>
> Any help you can provide about this issue is GREATLY appreciated.
>
>
>
>
>
>

I have the same problem, but more with PTR records. There are numerous
obsolete entries in our reverse look up zone and I am clueless on where the
problem is. Here's a breakdown:

2 Win2K SP4 DCs, same subnet, 255.255.255.0
One authorized as DHCP Server (192.168.1.x)
Both running DNS Service
Both hosting same Active Directory Integrated domain Forward Lookup Zone
(mycompany.intra)
Both hosting same Active Directory Integrated Reverse Lookup Zone for local
subnet of mycompany.intra (192.168.1.x)

"Allow dynamic updates?" is set to YES for Forward Lookup Zone
(mycompany.intra)
Aging/Scavenging set to 7 days for "no refresh" and "refresh" intervals
(This appears to be working as I get Event ID: 2501 every 7 days that stale
records were scavenged) the problem seems to be with PTR only

"Allow dynamic updates? set to "Yes" for Reverse Lookup Zone (192.168.1.x)
on each DC
Aging/Scavenging set to 7 (no-refresh) and 8 (refresh) days intervals

Dynamic DNS updates by our DHCP Server (Option 81) is also enabled.

Based on the above, why are PTR records still not updating or getting
removed? Maybe I'm overlooking something? All client computers are Windows
XP. We need the capablity to do reverse lookups of an IP to the correct
HOSTNAME for various reasons. Other network software relies on these
accurate lookups.

Thanks in Advance







"ILKER SOGUT" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> As far as I understand you habe a problem with the config of "Aging and
> scavening period"
>
> At your DNS server properties first enable the "Set Aging and Scavening
> ..." its default perioed to clean old datas 7 days
> check it
>
> Good Luck
>
> ILKER SOGUT
>
> "-=M@rk=-" <someone@(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I ran across this issue a few days ago and can't seem to find anything on
>>Microsoft's site to solve the problem.
>>
>>
>>
>> Under DNS Management (dsnmgmt) I have noticed that under my .local there
>> many machines listed under there that are no longer a part of my network.
>> I have also noticed that some of the machines are listed more than once
>> and that some even have the same IP address.
>>
>>
>>
>> I have looked at the DHCP server and it seems to be working fine. I have
>> addresses set to renew ever hour as I was testing to see what might be
>> causing the problem.
>>
>>
>>
>> It just doesn't seem that DNS is cleaning up after itself.
>>
>>
>>
>> Any help you can provide about this issue is GREATLY appreciated.
>>
>>
>>
>>
>>
>>
>
>