Re: DNS record time stamp replication
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 22:32:36 -0400
In news:CFFE3B1E-1D49-4973-9DE8-6483D28A66DA@xxxxxxxxxxxxx,
Troy Schaffranek <TroySchaffranek@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post,
which I then commented about below:
> But in my lab all of the dynamic entries seem to be updating and
> replicating OK. Here's an instance in production in which I can see a
> dynamic DNS client (but a static IP) not have a current time stamp:
>
> Here's the DNS debug log traffic:
> 20050815 16:12:15 F68 PACKET UDP Rcv 10.9.50.240 b825 U [0028
> NOERROR] (6)domain(2)domain(8)domain(2)domain(2)domain(0)
>
> 20050815 16:12:15 1DC PACKET UDP Snd 10.9.50.240 b825 R U [00a8
> NOERROR] (6)domain(2)domain(8)domain(2)domain(2)domain(0)
>
> 20050815 16:12:15 F68 PACKET UDP Rcv 10.9.50.240 9527 U [0028
> NOERROR] (2)50(1)9(2)10(7)in-addr(4)arpa(0)
>
> 20050815 16:12:15 1EC PACKET UDP Snd 10.9.50.240 9527 R U [00a8
> NOERROR] (2)50(1)9(2)10(7)in-addr(4)arpa(0)
>
> But when I check all 8 DNS servers they all show the same <very old>
> time stamp. Here's the dnscmd /enumrecords /detail:
>
> Returned records:
> RPC Node:
> ptr = 000888B0
> wLength = 16
> wRecordCount = 1
> dwChildCount = 0
> dwFlags = 00800000
> Node Name = @
> A Record info:
> ptr = 000888C0
> wType = A (1)
> wDataLength = 4
> dwFlags = f0
> rank = f0
> dwSerial = 00000000
> dwTtlSeconds = 1200
> dwTimeStamp = 3544558 ([22: 0: 0] [ 5/12/2005])
> A 10.9.50.240
> Command completed successfully.
>
> Any thoughts? I'd really like to tenable scavenging but I'm afraid
> I'm going to whack a bunch of needed entries.
>
They look like static entries, but static records have a zero (0) TTL.
You're n. Scavenging will remove aged records. If the records have that long
of a TTL, scavenging won't remove them. If dynamic updates are working
properly, when the machine gets shutdown properly it will remove it's own
record. If it gets a new IP (DHCP), it will remove it's old record and
dynamically update the new record.
I'm looking at your origianal question about if TTLs get replicated. If the
record is created say on DC1, then DC1 is the SOA of that record. It will
get replicated by the normal AD replication process with that TTL. Do you
believe you are having AD replication problems?
Here's some more info about scavenging.
Understanding aging and scavenging- Domain Name System(DNS):
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/92d228d2-4fe2-40b9-88a7-2a5a2bee8508.mspx
Enable Aging and Scavenging for DNS- Active Directory:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/7e953411-6f0b-462e-9008-320a949b0fa0.mspx
Managing the aging and scavenging of server data- Domain Name System(DNS):
(This has TTL info about dynacmically updated records:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/528aa0a4-e5b4-45da-9769-1d00ef636bb3.mspx
I hope they help.
Ace
.
- Follow-Ups:
- Re: DNS record time stamp replication
- From: Troy Schaffranek
- Re: DNS record time stamp replication
- References:
- DNS record time stamp replication
- From: Troy Schaffranek
- Re: DNS record time stamp replication
- From: Ace Fekay [MVP]
- Re: DNS record time stamp replication
- From: Troy Schaffranek
- Re: DNS record time stamp replication
- From: Ace Fekay [MVP]
- Re: DNS record time stamp replication
- From: Troy Schaffranek
- DNS record time stamp replication
- Prev by Date: Re: Import from HOST file
- Next by Date: Re: Event ID 5504 - Windows 2003 DNS
- Previous by thread: Re: DNS record time stamp replication
- Next by thread: Re: DNS record time stamp replication
- Index(es):
Relevant Pages
|