This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 17%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
I am having an issue where no devices with a DHCP address are registering a PTR record in the reverse DNS zone.
Some background on the setup: DHCP and DNS are being run off of a Active Directory domain controller, which is running Server 2016 and happens to be the FSMO. There is a second DC which is also running DNS on Server 2012 R2. Devices that are configured with static IP's register both their A and PTR records to both DNS servers. These static devices consist of Windows and Linux OS's, all of which are domain joined. Devices that are assigned a DHCP address will register an A record (if they are domain joined, as expected) but never register a PTR record. This happens for any device, workstations, severs, VoIP phones, WAPs, etc.
The forward lookup zone has dynamic updates set to secure only. I have tried toggling this setting on the reverse zones between secure and both with no effect. The DHCP scopes are set as shown to always dynamically update DNS.
I went to a few of the dynamically generated A records and checked the "Update associated PTR record" box and those few devices did generate PTR records and have been updating them, and confirmed lookups on those records return the correct info. This is the only way to populate the dynamic PTR records I have found, even net new workstations only generate an A record within the DNS servers.
Any guidance or recommendations would be great
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Some other things to look at.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-dns-dynamic-updates-windows-server-2003
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
DSPatrick,
Again thanks for the reply, that link was very useful. I read through the document and it confirmed that the setup I am looking for is indeed possible and supported: "You can configure a Windows Server-based DHCP server so that it dynamically registers host A and PTR resource records on behalf of DHCP clients"
Furthermore, it reaffirms that my DHCP/DNS is not functioning as intended: "By default, Windows-based DHCP clients are configured to request that the client register the A resource record and that the server register the PTR resource record."
This leads me to believe that the DHCP services on the server are failing to register any DNS records to the DNS service running on the same server, as the only records that populate in DNS are either manually created by an admin or from the client device.
I went ahead and created a new AD user for DHCP authentication and entered that info into the DHCP dynamic registration credentials, and it looks like a handful of PTR records have been generated across the subnets. I'll have to wait for all of the devices to send out DHCPREQUEST broadcasts to see if this corrects the issues, so far only domain joined Windows devices have populated records. Thanks for pointing me to the right resource.
Glad to hear of this progress, you're welcome.
On the problem member check that this one is checked.
--please don't forget to upvote and Accept as answer if the reply is helpful--
DSPatrick
Thank you for the fast response
Enabling that option on a workstation does indeed populate the PRT record on the DNS server. However I would rather not have to enable this across all devices in the domain, and this does not address the issue of the non-windows devices. I was hoping for a server side method that is device/OS agnostic if possible
I don't know why it isn't defaulted this way but maybe this one helps.
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/062978ce-54bb-417e-9459-8293b53d6e2d/dnsregisteredadapters-dns-suffix?forum=ITCG
--please don't forget to upvote and Accept as answer if the reply is helpful--
Again, this addresses the issue for domain joined Windows clients, but none of the other devices/OS's. If there is no mechanism to accomplish this server side with my setup, that's fine, I can tolerate a more involved approach like this, I would just rather use it as a last resort.
