Re: DNS record time stamp replication

Tech-Archive recommends: Fix windows errors by optimizing your registry

In news:6F4779B0-6361-4DAE-8DF5-F711E764AE75@xxxxxxxxxxxxx,
Troy Schaffranek <TroySchaffranek@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post,
which I then commented about below:
> All of my domain controllers are Windows Server 2003 w/SP1 and are DNS
> servers. DNS is AD integrated. DHCP clients are registered
> dynamically using DNS proxy from the DHCP servers.
>
> Currently DNS scavenging is not enabled on the zone for the AD
> domain. I want to enable it. The plan was to enable scavenging on
> only one of the servers to reduce replication traffic. The problem is
> this...
>
> If I look at the DNS record time stamp on AD1 for the DHCP registered
> client "xyz", the time stamp shows 5/10/2005 6:00:00 PM. This is bad
> because if scavenging were enabled (it hasn't been for some time on
> the zone) this record would be purged. I'm using 7 days for the no
> refresh period and 7 days for the refresh interval so if it is older
> than 14 days it gets scavenged.
>
> I enabled debug logging on AD1, AD2 and AD3. This morning I searched
> the DNS debug logs for the IP of "xyz". I found activity of it on
> AD3. I looked at AD3's DNS record time stamp and it shows 8/5/2005
> 10:00:00 AM. AD1 still shows 5/10/2005 6:00:00 PM and AD2 shows
> 5/10/2005 6:00:00 PM.
>
> My question is whether or not the DNS time stamp attribute is
> replicated because it doesn't appear that way to me? If it is is
> there a configuration option I am missing?


You should enable scavenging on all DNS servers with the same exact settings
to keep consitent because AD Integrated zones also means multi-master
behavior, which in turn means any server can be the SOA of a record.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================


.

Relevant Pages

  • Re: Duplicate HOST A record entries on the reverse lookup Zone
    ... then 24 and did the manual/ start scavenging of the stale resource records ... Used the DHCP server to update DNS records: ... "Set Aging/Scavenging for All Zones. ...
    (microsoft.public.windows.server.dns)
  • Re: Dynamic DNS, DNS Records & Scavenging
    ... There are two DHCP ... Both the servers are set to update A and PTR records for clients. ... DNS however this doesn't seem to be the case. ... DNSUpdateProxy and when i did this i saw my test laptop register its ...
    (microsoft.public.windows.server.dns)
  • Re: Static IP timestamp
    ... I just tested this withWindows 2003 DNS. ... When I had built a few servers for a customer and let them auto register, they had a timestamp and the scavenge checkbox was checked. ... Unless you are seeing something going on that is affecting your environment, the default settings work fine, at least they do for me for all of my customers and installations I've worked in that I've set scavenging and forced DHCP to own the records so it can update the records it had registered at lease refresh time. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Scavenging
    ... We are planning to turn on DNS Scavenging and are ... Not to delete the DNS record when it becomes stale etc.. ... The nice thing about DHCP ... Force DHCP to register all records, Forward and PTR, (whether a client ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Scavenging Configuration Settings
    ... DHCP server in each one or as already suggested use superscopes on your ... current default DNS scavenging settings ... their DNS records at least once every 24 hours. ...
    (microsoft.public.windows.server.dns)