Dhcp not updating lease

Even when registering DNS on the client, nothing is added on the DNS servers.

dhcp not updating lease-6dhcp not updating lease-35dhcp not updating lease-46dhcp not updating lease-22

I pinged wxp-38-shop and it shows a different IP than what is given in the Address Leases page (Windows 2003 Server). This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Of course the ping results time out because that IP no longer exists.

Despite it being a DHCP Option, it’s not found in a DHCP server, scope or class option. You must delete them manually to allow DHCP to take care of all new records moving forward. Quoted from the following link: “Name squatting occurs when a non-Windows-based computer registers in Domain Name System (DNS) with a name that is already registered to a computer running a Windows® operating system.

Also, it will allevaite another issue – If DHCP is on a DC, it will not overwrite the original host record for a machine getting a new lease with an IP previoulsy belonging to another host. The use of Name Protection in the Windows Server® 2008 R2 operating system prevents name squatting by non-Windows-based computers. There are some misconceptions prompting fears that Scavenging will remove everything in your zone, includind servers.

On a semi related note: I know this has been a touchy subject some places I have looked. For each DC, what should their local DNS settings be?

To the client it looks like a "normal" lease is allocated, but on the server the fixed-address clients go through a completely different code path.

Leave a Reply