Dns is not updating from dhcp server
We hope this primer to troubleshooting dynamic DNS updates was able to point you in the right direction to the problem -- and a solution.When a problem occurs start from the client and work your way back.The following list illustrates a typical example of how a private DNS update leaks out to the global Internet. The DHCP client first sends a query to its local domain name server (LDNS) and asks for the authoritative server for the zone of its domain name (step 3).Once the DHCP client receives a response (step 4), it sends the update to the indicated server (step 5).Check the DNS client service of the new computer The DNS client service is the service that does the actual update.If this service is stopped for some reason no update will proceed.
In the example shown above, the LDNS is not configured with a local zone for 168.192.
Only if you know with certainty that the updates get sent only to a local DNS server should you run the Dynamic DNS Updates service.
Most home users who use DSL/Cable routers as DHCP/NAT servers to facilitate multiple host connections to the Internet should turn off dynamic DNS updates.
Microsoft Dynamic DNS (DDNS) is a wonderful feature.
Combined with Active Directory (AD) it makes managing thousands of DNS records for clients and servers a breeze.