However, so that other computers can find this new device, the DHCP server should also go update the forward and reverse lookup zones in DNS dynamically.
The end result being that if you connect a device to the network called “mainpc01”, within a few seconds of you getting an IP address, on another machine, I should be able to “ping mainpc01”On the DHCP server, at the scope level – right-click and choose Properties and click on the DNS tab: I have it set up this way because I especially wanted this for non-Windows machines.
In other words, the Windows AD member client already knows how to request DHCP to register/update the ‘PTR’ DNS record, but how the heck do you configure the Windows AD member client to also request DHCP to register/update the the ‘A’ DNS record? In this case you will see that after the DDNS registration/update the ‘A’ DNS record is owned by the computer account of the AD member client and the ‘PTR’ DNS record is owned by the user account specified as DDNS credentials in DHCP.
With this configuration the DHCP server will always register a DNS record on behalf of the DHCP client whether or not that DHCP client actually requests it.
So, right-click on a forward-zone: and choose Properties: Here you just want to make sure Dynamic updates is set to secure, ideally.
found a way to configure a Windows AD member client to request the DHCP server to register/update BOTH the ‘A’ DNS record and the ‘PTR’ DNS record! According to the information in With this configuration the DHCP server will register a DNS record on behalf of the DHCP client only when that DHCP client actually requests it.
With the help of DNS integration with the DHCP, you can simplify this task and can remarkably reduce the administrative overhead.
What I wanted is this: Your DHCP server gives out an IP address.In this case you will see that after the DDNS registration/update both the ‘A’ DNS record and the ‘PTR’ DNS record are owned by the user account specified as DDNS credentials in DHCP.In the "DHCP Request" message you can see the DHCP client is requesting to self-register the ‘A’ DNS record.Plusnet has told its customers to use static LAN IP addresses and fixed DNS settings, rather than obtaining this information automatically via DHCP, to reach the web.Subscribers have told El Reg that a simple reboot is not always effective at clearing the problem: sometimes it takes multiple restarts to pick up network settings automatically.Specifically, it seems some Windows 10 and 8 boxes can no longer reliably obtain LAN-side IP addresses and DNS server settings from their BT and Plusnet broadband routers, preventing them from reaching the internet and other devices on their networks.