A graphical representation of the timeline of the no-refresh and refresh intervals and the scavenging period is at the bottom of the article. Those are my settings. We have over devices on the domain and an addition BYOD.
This setting has been working fine for me over the last two years. I say go for it. The real problem is going to be all those duplicate dns records. To your specific example, if you have both intervals set to 7 days, then assuming there were no refreshes to the record on the 14th day, the record would become eligible for scavenging.
But it wouldn't actually be scavenged until the next scheduled scavenging period or you clicked "scavenge now".
Great, I think I'm going to stick with the default settings for now. I have read that article but am going through it again.
Thanks everyone for the advice and help! In general, all dynamicly leased DHCP IP addresses will the time when they were lst registered and thus are elegible for scavenging. So be very careful! All my main servers as well as printers have static addresses.
The DHCP lease is set up for 2 days so by the time 14 days hit the devices would have a time stamp a max of 2 days right? I have noticed that there are old entries of test server, test PCs old name, so should I run the Scavenge SRR, so just right click and delete the entries. If I turn on Scavenging within the zone then it should be enough and the records should be deleted, right?
As part of the DNS server, Scavenging has an additional option to specify the days in the zone that does not exist. Can someone explain this? Authorizing a DHCP server in workgroup.
Skip to main content. Find threads, tags, and users Need help! Thanks in advance! Comment Show 0. Current Visibility: Visible to all users. Hi Candy, Thank you very much for your reply. The article you recommended is very helpful. If not, the clock is ticking. I set the scavenging period to occur daily. Right-click the server node and click Properties.
Select the Advanced tab, then place a check in the Enable automatic scavenging of stale records box. Set your scavenging period, and click OK.
Your scavenging period simply defines how often the process will run, akin to a scheduled task. Alternatively, if you prefer to set the values per-zone, right-click the zone and click Properties. Select the General tab, click Aging , and place a check in the Scavenge stale resource records box. Set your No-refresh interval and your refresh interval, and click OK.
Finally, if you need to configure resource record settings, you need to enable the advanced view in your DHCP management console. Click View , then Advanced. At this point, you can right-click a record, select Properties , and place a check in the Delete this record when it becomes stale box. Static records will not. The process works well in most cases and keeps DNS clean. From within the same DHCP management console, right-click each scope, click Properties , select the DNS tab, and ensure the same options are configured.
If you have a larger environment with many DNS records, you may want to test the aging process before you enable scavenging.
You can configure aging on your DNS zones and records, but not enable scavenging on the server.
0コメント