Dhcp not updating dns forward lookup zone
The DHCP server will use this information, along with its dynamic update configuration, to determine whether or not the DHCP server will perform the PTR record update against the authoritative DNS server on behalf of the client, or if the client will perform the PTR update against the authoritative DNS server on its own. The first step of this process still involves the client machine sending an SOA-type query to the configured DNS server.The client then receives information from the authoritative DNS server indicating which server will be processing the update.The DHCP server in this case is NOT a windows server. The only thing I had to do after this was, flush the dns entries on the clients with: ipconfig /flushdns After this they have poped up in my reverse lookup zone. The fix of adding the DHCP server to DNSupdateproxy group solved my issues. I guess that the forward lookup records are created by the host, but the reverse records are created by the DHCP server? Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free.
From there, the client continues communicating with the primary DNS server that accepted the A record update.If so, your DHCP server may not be configured to auto-register their IP with the DNS server.To check, right-click your DHCP scope and go to properties.This article covers the default security settings for DNS zones: the settings are jacked up (or even if they are fine), you might try just blowing away the reverse zone and recreating it since you basically have a non-functioning reverse zone as it is...Try running an "ipconfig /registerdns" on one of the clients and see if it adds a record to the reverse zone.
Search for dhcp not updating dns forward lookup zone:
From there, the client continues communicating with the primary DNS server that is accepting the PTR record update.