In this chapter, you'll learn how to implement a DHCP server, including the installation process, authorization of the server, and the configuration of DHCP scopes.
The chapter ends by looking at how to manage a DHCP server and monitor its performance.
You bring the new computer online and it obtains a DHCP lease for the same IP address. However, when you try to resolve the name of the new computer, the old computer's name still comes up. Here's how we'll start the troubleshooting process: 1.
Check the DNS client service of the new computer The DNS client service is the service that does the actual update.
Probing the DNS servers via dig returns no records for the hostname.
Windows DHCP clients in the domain which have reservations properly update DNS. Are your DHCP servers set to update DNS even with an unauthenticated requests?
Static IP addresses can add a lot of administrative overhead.
Not only can management of static IP addresses become time consuming, but such management also increases the chances of misconfigured parameters.
To successfully update, the AD computer account needs to have Modify rights to its own dns Node AD object.
This can get complicated so if you suspect this is the case, we advise checking out this blog post entitled How to Fix Dynamic DNS Record Permissions Automagically. Temporarily enable DNS debug logging on your DNS server Enabling debug logging on your DNS server allows the server to begin generating a debug log of all dynamic update activity. We have a Power Shell script to ease the pain by displaying the content in a more user-friendly format.
In the DHCP server interface, I can see that the hostname of the client is properly being displayed, so I know the client is properly sending the hostname back.