none
PTR records fail to update

    Question

  • I recently migrated some DHCP servers from 2008r2 to 2016 and some of them are having issues registering DNS PTR records for DHCP leases.  Servers are fully integrated DCs running DHCP/DNS/GC.

    I receive this error in the event log (DHCP-Server 20322 -- Name Registration.)...

    PTR record registration for IPv4 address [[172.19.1.241]] and FQDN PC123.XXX.com failed with error 9005 (DNS operation refused.

    ).

    Also, in the DhcpSrcLog-DAY.log i receive these entries

    31,05/16/18,00:01:29,DNS Update Failed,172.19.1.241,PC123.XXX.com,,,0,6,,,,,,,,,9005  

    and occasionally 

    31,05/16/18,00:01:00,DNS Update Failed,172.19.1.37,PC124.XXX.com,,,0,6,,,,,,,,,9004

    The DHCP scope is set as it should be...


    And under the DHCP server's IPv4 "Advanced" tab I have entered the credentials of a user that is a member of the "DnsUpdateProxy" group.

    All of the forward look zones register just fine.

    I simply cannot find anything on that event log I'm getting.

    Looking for some assitance.

    Thanx!

    Wednesday, May 16, 2018 3:38 PM

Answers

  • I've solved to problem.

    The issue was that there was never a reverse lookup zone created.  The site is a /22, and we did create a zone for 172.19.0, but as reverse zone are not subnetted, we never had one for 172.19.1, 172.19.2., or 172.1.3.   Once I created the additional zones, all was well.

    Thanks!

    • Marked as answer by kered248 Thursday, May 17, 2018 7:02 PM
    Thursday, May 17, 2018 7:02 PM

All replies

  • Hi,

    Thanks for your question.

    About events have error code "9005", which means the DHCP server cannot update the record as does not have sufficient rights to it. This can happen for records that were created by the client or DNS manually in the DNS console. They have an ACL that does not include an account for registration from the DHCP settings.

    Please try the following link that is a similar thread as yours to check the DHCP option for DNS server. The DHCP server will select the first DNS in option 006 to use for the updates as the exhibit in this link.

    https://social.technet.microsoft.com/Forums/windows/en-US/038e1482-d7cc-4b8b-af2a-c4c915a83191/dhcp-not-updating-dns?forum=winserveripamdhcpdns

    In addition, here is the article discussed about the troubleshooting for the issue dynamic DNS registration form a MS DHCP server either fail or is delayed.

    Dynamic DNS registration process can cause queue build up and failures

    https://blogs.technet.microsoft.com/networking/2016/11/25/dynamic-dns-registration-process-can-cause-queue-build-up-and-failures/

    Hope this helps. I look forward hearing your good news. If you have any questions, please feel free to let me know.

    Have a nice day!

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    • Marked as answer by kered248 Thursday, May 17, 2018 6:55 PM
    • Unmarked as answer by kered248 Thursday, May 17, 2018 6:56 PM
    Thursday, May 17, 2018 4:32 AM
  • I've solved to problem.

    The issue was that there was never a reverse lookup zone created.  The site is a /22, and we did create a zone for 172.19.0, but as reverse zone are not subnetted, we never had one for 172.19.1, 172.19.2., or 172.1.3.   Once I created the additional zones, all was well.

    Thanks!

    • Marked as answer by kered248 Thursday, May 17, 2018 7:02 PM
    Thursday, May 17, 2018 7:02 PM
  • I'm very pleased for your issue was resolved successfully. Thank you for sharing in the forum as it would be very helpful to others. 

    Highly appreciate your effort and time.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, May 18, 2018 3:00 AM