DHCP on DNS, Scavenging and the DnsProxyUpdate Group:

            The entity that registers it owns the record. The nice thing about DHCP
owning the record is it will update it if DHCP gives the machine a new IP.
Otherwise you'll see multiples of the same in DNS whether scavenging is
enabled or not. I would force DHCP to own the record as well as enable
scavenging to keep it clean. To force DHCP to own the record, you will need
to do the following:

1. Add the DHCP server to the DnsUpdateProxy Group.
2. Force DHCP to register all records, Forward and PTR, (whether a client
machine can do it or not) in the Option 081 tab (DHCP properties, DNS tab).
3. Set Option 015 to the AD domain name (such as example.com).
4. Set Option 006 to only the internal DNS servers.
5. If the zone is set for Secure Updates Only, then DHCP cannot update
non-Microsoft clients and Microsoft clients that are not joined to the
domain. In this case, you will need to create and configure a user account
for use as credentials for DHCP to register such clients.

If your DHCP servers are Windows 2003 or WIndows 2008, Configure a
dedicated the user account you created as credentials in DHCP by going into
DHCP COnsole, DHCP server properties, and on the Advanced tab of the DHCP
Server Properties sheet click the Credentials button, and provide this account

The user account does not need any elevated rights, a normal user account
is fine, however I recommend using a Strong non-expiring password on the

Once you implement scavenging, you will need to wait at least a week for it
to take effect. You can quicken it up by manually deleting the incorrect
records to get started.

But more importantly, if DHCP is on a DC, it will not overwrite the
original host record for a machine getting a new lease with an IP
formerly belonging to another. To overcome this, add the DHCP server
(the DC) to the DnsProxyUpdate group. This will force DHCP to own
all records it will create moving forward and will update an IP with
a new name in DNS.

If you set this, but when a record shows up in the DHCP Lease list with a
pen (which means that a write is pending), it m ay mean it is trying to register
into a zone that does not exist on the DNS servers. This happens in cases
where the client machine is not joined to the domain and has a missing or
different suffix than the zone in DNS. It can only register into a zone that exists on
DNS and that zone updates have been configured to allow updates.

If this is the case, go into the client machine's IP properties, and
on the DNS tab in TCP/IP properties, clear the "Register this connection's
addresses in DNS" as well as the "Use this connection's DNS suffix in DNS
registration" check boxes, the DHCP Server will fill these in for you and register using
the domain name in Option 015.

Popular posts from this blog

AD LDS – Syncronizing AD LDS with Active Directory

DNS Scavenging.