A RR Timestamp not Updating

  • Thread starter Thread starter Lisa
  • Start date Start date
L

Lisa

I have a Windows 2000 DNS Server that has a Active-
Integrated forward-lookup zone. The forward-lookup zone
is configured for secure dynamic updates. I also have a
reverse lookup zone configured for each subnet.

When a W2K or WXP client first registers to DNS, the A RR
and PTR record are created fine with a timestamp of the
date the record was created.

However, it has been over 6 months and the A RR timestamp
is not updating as it should. The PTR record has been
updating fine. From my understanding, both the A RR and
PTR timestamp should update during normal DNS refreshes
(e.g. running ipconfig/registerdns, rebooting the
workstation, or default 24 hour refresh period). The
workstation is a DHCP client, but the DHCP server is not
configured to update DNS information for the DHCP client
because DHCP is running on a DC.

I am wondering what do I need to do to make sure the A RR
timestamp updates properly.
 
In
Lisa said:
I have a Windows 2000 DNS Server that has a Active-
Integrated forward-lookup zone. The forward-lookup zone
is configured for secure dynamic updates. I also have a
reverse lookup zone configured for each subnet.

When a W2K or WXP client first registers to DNS, the A RR
and PTR record are created fine with a timestamp of the
date the record was created.

However, it has been over 6 months and the A RR timestamp
is not updating as it should. The PTR record has been
updating fine. From my understanding, both the A RR and
PTR timestamp should update during normal DNS refreshes
(e.g. running ipconfig/registerdns, rebooting the
workstation, or default 24 hour refresh period). The
workstation is a DHCP client, but the DHCP server is not
configured to update DNS information for the DHCP client
because DHCP is running on a DC.

I am wondering what do I need to do to make sure the A RR
timestamp updates properly.
Click to expand...

Could be a permissions issue, is "allow dynamic updates" set to "Yes" or
"Only secure updates"
If secure, change to "yes" and run ipconfig /registerdns to see if the time
stamp is updated.

If set to "Yes" post netdiag /v /test:DNS and post ipconfig /all
 
Never mind I found the answer. Since I don't have
Scavenging turned on, the timestamp will not update.

Thanks
 
Back
Top