Windows dns not updating from dhcp
A quick Facebook read the first line and click “Like,” seems to be the norm. And yea, I had to state Windows 2000 and newer, because this stuff doesn’t apply to older Windows versions.
Well, I will also offer the nitty gritty below the summary for those who want to read. But DHCP will register its PTR (reverse entry) record.
``So what if my host leaks a few packets to the global Internet? '' The reason is that inconsistent configuration between your home hosts and your local DNS servers can, and often does, cause leakage of DNS updates for private IP addresses to the global Internet.
In the correct setup, the LDNS should point the DHCP client to a domain name server (could be itself) inside the internal network.
The LDNS thus iteratively sends the SOA request, starting with a root DNS server, and eventually returns the server (step 8).
Over 97% of DNS updates that leak onto the global Internet come from Microsoft Windows operating systems (see companion paper on The Windows of Private DNS Updates).
Note: “This is a modified configuration supported for DHCP servers running Windows Server 2008 and DHCP clients.
In this mode, the DHCP server always performs updates of the client’s FQDN, leased IP address information, and both its host (A) and pointer (PTR) resource records, regardless of whether the client has requested to perform its own updates.” “With secure dynamic update, only the computers and users you specify in an ACL can create or modify dns Node objects within the zone.