Solution: Verify that the client is fully and correctly configured for DNS, and update its configuration as needed.
Domain Name Server (DNS) used for name resolving to any hosts.
Master DNS servers (Primary Server) are the original zone data handlers and Slave DNS server (Secondary Server) are just a backup servers which is used to copy the same zone information’s from the master servers.
Thus these long process will just resolve with in milliseconds.
If they don’t know the request they will reply as NXDOMAIN.
You can use the ipconfig /registerdns command option to manually force a retry of the client computer's dynamic registration.
For computers running earlier versions of Windows, you can use the options of the ipconfig command to verify, view, or renew the client TCP/IP configuration details as appropriate.
// options ; logging ; zone "." IN ; ## Define our slave forward and reverse zone, Zone files are replicated from master. Now time to configure our client machines and check for the hostname.
zone"tecmintlocal.com" IN ; zone"0.168.192.in-addr.arpa" IN ; ##### include "/etc/named.rfc1912.zones"; include "/etc/key"; After restarting the bind service, we don’t have to define the zone information individually, as our allow-transfer will replicate the zone information from master server as shown in the image below. In client side we need to assign the Primary (192.168.0.200) and Secondary DNS (192.168.0.201) entry in network settings to get assign a hostname.
If the DHCP server succeeds in performing the update with the DNS server, the result is an updated DNS host name and updated IP address information for the client computer in the DNS database.