Re: RRs Not Refreshing in DNS

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Aug 5, 12:54 am, "Kevin D. Goodknecht Sr. [MVP]"
<ad...@xxxxxxxxxxxxxx> wrote:
Read inline please.

Innews:1186177438.600897.220540@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
tman <naves....@xxxxxxxxx> typed:

Many of the resources records in my dns servers are apparently not
getting refreshed. They were dynamically registered in dns weeks ago
but they do not have a time stamp and the "Delete this record when it
becomes stale" box is not checked. A reboot of the host does not
refresh the record, a ipconfig /renew does not refresh the record.
Only an ipconfig /release, ipconfig /renew refreshes it

Other than the records not having a time stamp, this sounds like the DHCP
server is registering the records, which is my preferred method in most
environments. If the DHCP server registers, de-registers and owns the
records and the DHCP server is set up correctly, you don't need to enable
scavenging, unless you just want to.

1, Clear the register this connection's addresses in DNS on the clients.
2, Create a dedicated user account with a non-expiring strong password for
DHCP to use in DNS registration.
3, In the DHCP Console on the Properties *** of the DHCP server(s),
Advanced tab, Credentials button, enter the credentials of the user account
in Step 2.
4, Select the DNS tab.
a, Enable DNS dynamic updates(Checked)
b, Always dynamically update DNS A and PTR records.(Selected)
c, Discard A and PTR records when lease is deleted(Checked)
d, Dynamically update DNS A and PTR records for clients that do not
request updates(Checked, overrides Step 1 on client configuration)
5, Add Advanced Microsoft Windows 2000 options 001 (0x0 enables NetBIOS)
and 002 set to 0x1 to release the Lease on shutdown.
6. Add Standard DHCP option 015 with the domain name of the zone to be
registered in.
7, Set the lease to 1 day or so.

With these settings, the DHCP server will register the records, update the
records, and remove the record when the client shuts down. It will also
cause DHCP to remove records for clients that are suddenly disconnected from
the Network such as laptops.



I just enabled Aging/Scavenging on my one Forward Lookup Zone to try
it our before configuring it on the several Reverse Lookup Zones that
I have and setting it to do it automatically. It seems to me that
unless the resource records are refreshing, Aging/Scavenging will not
work.

Is there a way to get these hosts refreshing their dns records short
of going to each host in the company and typing ipconfig /release,
ipconfig /renew ?

ipconfig /release && ipconfig /renew
or just reboot the client.

I tested this and the only thing that changes the A record to give it
a time stamp and check the "Delete this record when stale" box is an
ipconfig /release and ipconfig renew. A reboot does not do it. This
involves a visit to each of 400 hosts.

Thanks for the info on letting the DHCP server handle the "scavenging."

.

Quantcast