In no-refresh interval, the record time stamp is not changef even if DHCP
(or client) requests a refresh after the first update. In refresh iterval
the DHCP (or the client) is given a chance to update.
To set it to minimum or to maximum will depennd on your network, which
clients will be updating through the DHCP.
If it is normal clients - just domain members, then you can set it to say 1
day each.
Or if you are an ISP, serving dynamic IP to various clients, you should set
it to minimum.
Once this is set in zone properties, the setting in server properies is
over -rided.
The setting in server properties, will be applied for the zones, for which
you have not seperately set these peroprties.
Sharad
"Cyberndj" <Cybe...@discussions.microsoft.com> wrote in message
news:78DEBC02-BED7-48C9...@microsoft.com...
Thanks
The scavenging won't delete the records until the time stamp on the records
expire. Have you verified the time stamp on the records are older than the
number of days set to expire the records?
--
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
===================================
Chris also posted in another thread below, but it wasn't originated by
Chris. I had suggested for the original poster to use the DNSUpdateProxy
solution. That may work so DHCP takes ownership of the record and overwrites
the new records on top, but scavenging should do the trick.
-- Ace
Are you getting any Event log errors?
See if these help to explain a little on it. Most are for 2000, but they
pretty much apply to 2003.
296116 - HOW TO Configure the Windows 2000 Domain Name System to Age
Records:
http://support.microsoft.com/?id=296116
301644 - DNS Server Forced Scavenge Does Not Immediately Start Zone
Scavenging:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B301644
306780 - DHCP Does Not Delete DDNS PTR Record for Expired Leases:
http://support.microsoft.com/default.aspx?scid=kb;en-us;306780&Product=win2000
How to use DNS aging and scavenging:
http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windows2000/en/advanced/help/sag_DNS_pro_ConfigAgingScavengingNode.htm
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
Ace
In DHCP:
Each subnet has a different lease duration.
DHCP updates DNS automaticly.
In DNS:
We have mutiple zones running.
We have an active directory zone and a non ad zone.
Scavenging Settings will be:
No refresh is .5 of lease duration.
Refresh is same amount as uration.
Questions:
For each zone: Should the scavenging settings go off the shortest DHCP lease
or the Longest DHCP Lease, and why?
For the Server: Should the scavenging settings go off the shortest Zone or
the Longest zone, and why?
Thanks
cyb
To understand what the setttings will do based on your lease lengths, this
article shows that info (it's a link in one of the articles I posted). I
believe they will answer your questions. It also has examples. One such
example says, the settihings need to be at least half of the DHCP lease
period, since at the 50% mark, is when a client will refresh its lease. Make
sense? Read on please for more info...
http://www.microsoft.com/windows2000/en/advanced/help/sag_DNS_und_AgingScavenging.htm
http://www.microsoft.com/windows2000/en/advanced/help/sag_DNS_imp_ManageAgingScavenging.htm
Ace