Dhcp not updating dns records
This association, or mapping, of an IP address to a domain name requires that a change in either the address or the name necessitates an update of the information in DNS.The DHCP protocol does not automatically update DNS in the event that the DHCP server changes the IP address of a client.When I installed active directory, I checked the option to install DNS but noticed that it did not create a "reverse lookup zone" so I created the zone afterward.I think I had trouble with DNS in the past when installing with AD, should perhaps it be installed BEFORE installing AD?Second, if your server goes down I would assume that your users inability to get to the internet would be the least of your worries, especially since this is a Domain Controller.If your really worried about your primary server going down for some reason, then, I would recommend setting up a second Domain Controller that runs DNS to use as a secondary DNS server.A flag of "0" means the client updates the A record and requests that the server update the PTR record on its behalf. Also in the DHCP scope make sure == Click the DNS tab, click Properties, and then click to select the Dynamically update DNS A and PTR records only if requested by the DHCP clients check box == is set.This would mean when the default flag of "0" comes in the server will then try to register the PTR record with the DNS server(s) it is configured to update.
They associate the TCP/IP address assigned by DHCP to a client with its fully qualified domain name (FQDN).The DNS Client service performs this function for all network connections on the client, including any that are not configured to use DHCP.When a qualified DNS client (such as a computer running Windows XP Professional or Windows Vista®) issues an update, DHCP servers running Windows Server 2008 process the update to determine in which of three ways the server will initiate updates on behalf of the client: The ability to register both A and PTR resource records enables a DHCP server to act as a proxy for clients running other operating systems, such as Microsoft Windows Millennium Edition, or Windows 98, for the purpose of DNS dynamic update registration.Did you create the subnet under reverse lookup zone the client & server belongs too, if no, the ptr record will not be created as subnet is missing for the client to register its ptr records.As article applies to windows 2003,hotfix is not applicable but reg setting can be done on windows 2008 R2 to resolve the issue. scid=kb; EN-US;837061 Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. X network] Also have you tried clearing the dns cache, clearing the controller cache (ipconfig /flushdns), reregistering the controller (ipconfig /registerdns), reconciling stale records and reloading the server datafiles???