I'm currently planning to perform DNS scavenging on one of our primary
forward lookup zones (AD integrated). We have 3 Win2003 Domain Controllers
all running DNS in our environment.

Before proceeding, however, I have a few items that need some clarification
and I would appreciate any advice from those in the know:

[1] Several days ago I went through the DNS records for this zone on our
primary DC to remove the "delete this record when it becomes stale" checkbox
from our static entries (server dns records). I went back today to recheck
them and I see that once again they are set to be deleted when they become
stale again. Why is this happening? I see on the other DC's that the same
record is not set for deletion though.

[2] In the forward zone I want to scavenge, there are the following sub
folders with records that are all set to delete when  they become stale:

- _sites\Default-First-Site-Name\_tcp\ (_ldap record for each DC)
- _tcp (_gc, _kerberos, _kpasswd, _ldap records for each DC)
- _udp (_kerberos, _kpasswd records for each DC)
- DomainDNSZones (A record for each DC)
- DomainDNSZones\_tcp\ (_ldap record for each DC)
- DomainDNSZones\_sites\Default-First-Site-Name\_tcp\ (_ldap record for each
DC)
- ForestDNSZones (A record for each DC)
- ForestDNSZones\_tcp\ (_ldap record for each DC)
- ForestDNSZones\_sites\Default-First-Site-Name\_tcp\ (_ldap record for each
DC)

Should I be unchecking the "delete this record when it becomes stale"  for
all these records on all 3 domain controllers?

[3] I realize that I must set scavenging at the server level and at the zone
level but do I want to set scavenging on all 3 DC's or just one? The DNS
zones are set to replicate "to all DNS servers in the Active Directory
domain".

Appreciate any feedback or advice anyone can offer on this matter. Thanks.

Hi Barkley Bees,

Please see in-line.

The servers in question will still have permission to update the record.
They will update the timestamp, and therefore update that box. If you
see differences between DCs check replication (or allow time for
replication).

I advise you allow those records to be scavenged anyway. For Host (A)
and Pointer (PTR) records the DHCP Client service will update each once
every 24 hours (this applies to clients with static IP addresses).

Making them completely static just gives you more work to do should you
decommission a server in teh future.

Show quoteHide quoteNo.

The NetLogon Service on the DC will maintain those registrations,
performing a Refresh once every 24 hours.

Just one. The settings on the zone will replicate to each server. And
the Scavenging task (Server Properties / Advanced) should only run on
one DNS server.

Because of the update intervals mentioned above I strongly recommend you
do not consider setting the Refresh Interval lower than 24 hours.

HTH

Chris

Linksys Wireless-N PCI Adapter
2 networks at the same time
My Documents Folder access
How to maintain server login password
Windows 2003 Srv - Losing Def Gateway
W2k8 - LAN + WAN - Windows FireWall and Advanced Security
LAC Properties Oddity
New Windows 2008 Server domain connection problem
Pre-Windows 2000 Name
Networked Devices