Not removing stale PTR records
Kellee
the A records update properly
thanks
Todd J Heron
>My 2003 AD integrated DNS using dynamic dns - is not removing old records.
>the A records update properly
>thanks
You need to turn on scavenging.
306780 - DHCP Does Not Delete DDNS PTR Record for Expired Leases:
http://support.microsoft.com/default.aspx?scid=kb;en-us;306780&Product=win2000
Are there any Event log entries related to Scavenging not working?
842463 - Event ID 2502 after you try to manually scavenge DNS resource
records in Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;842463
Here are some other links for more info:
You cannot scavenge old DNS records after you restart the DNS service:
http://support.microsoft.com/default.aspx?scid=kb;en-us;830689
DNS Server Forced Scavenge Does Not Immediately Start Zone Scavenging:
http://support.microsoft.com/default.aspx?scid=kb;en-us;301644
842463 - Event ID 2502 after you try to manually scavenge DNS resource
records in Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;842463
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
Kellee
refresh interval = 2 hours
Todd J Heron
>refresh interval = 2 hours
Scavenging needs to be turned on in two separate areas.
1) In the properties of the DNS server object itself.
2) In the properties of each ZONE on the DNS server that you want to be
scavenged
Kevin D. Goodknecht Sr. [MVP]
> Thanks - but scavenging is turned on.. with no-refressh interval = 1
> hour, refresh interval = 2 hours
You no refresh and refresh interval is way to short, unless you are running
ipconfig /registerdns hourly.
With the DNS console in Advanced View, click on the Aging button, what is
the date in "the zone can be scavenged after" field?
If it says something like 1/7/1601 scavenging won't work.
That said, this is pretty common in reverse lookup zones due to the
ownership of the records.
If you have DHCP set to update records and remove records when the lease
expires, DHCP won't be able to remove the records if the record is
registered by the client, since the client owns the record. Then if the
machine is suddenly disconnected, as in the case of a laptop, and the lease
expires DHCP cannot remove the record. Then, another machine connects, and
DHCP gives the IP out to another machine, the second machine cannot update
the PTR because it does not own the record, it is owned by the previous
machine.
IT sounds like a catch-22 doesn't it?
The way I handle this is I set DHCP to own all DHCP records by setting DHCP
to "Always update DNS" then when the lease expires, even if the machine is
no longer connected DHCP can delete the record.
I have also enabled Microsoft option 002, for release DHCP lease on shut
down. Which releases the lease and deletes the records on shutdown. This
won't help for machines that are suddenly disconnected, but it does for
machines that are shut down and then another machine obtains the lease on
the IP, while the previous lease holder is offline.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================