PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server

techcoor 1,251 Reputation points
2021-05-08T22:35:56.27+00:00

dcdiag /test:dns /v /s:DC1

PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.168.1.220 [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS delegation for the domain _msdcs.DC1. is broken on IP 192.168.1.220

           [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,457 questions
Accepted answer
  1. techcoor 1,251 Reputation points
    2021-05-12T21:33:25.437+00:00

    Not Sure now to check DNS name resolution for that one server.
    What I did was remove the Unknown a second time in Forward Lookup Zone. But this time I added 192.168.1.220. For the Reverse Lookup Zone, I selected edit, then Resolve and selected 192.168.1.220.
    That seemed to fix the PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server

    0 comments

8 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. techcoor 1,251 Reputation points
    2021-05-09T00:15:39.157+00:00

    The https://support.serviceshub.microsoft.com/supportforbusiness requires $500 to submit a problem.

    0 comments
  2. Sunny Qi 10,896 Reputation points Microsoft Vendor
    2021-05-10T05:26:47.653+00:00

    Hi,

    Thanks for posting in Q&A platform.

    PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.168.1.220

    The error may caused by the DNS server 192.168.1.220 doesn't host a reverse lookup zone. As far as I know, the error is harmless and you could ignore it.

    DNS delegation for the domain _msdcs.DC1. is broken on IP 192.168.1.220

    Please first verify that the delegation records are correct. Check out all "Name Servers" tabs for all forward lookup zones and reverse lookup zones. Locate all servers with <unknown> in "IP Address" field and remove them.

    Open DNS Management console > navigate to your "carousel.local" forward lookup zone and expand it. Double click on the delegation for _msdcs (kind of a faded icon) to expand it, then you can right-click it and select properties. Delete invalid entries, then add new ones, using FQDNs for DNS servers that have the _msdcs.carousel.local forward lookup zone.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  3. techcoor 1,251 Reputation points
    2021-05-11T15:50:42.747+00:00

    To tried to clean up this case I tried to delete replies to another community expert who disappeared. The Microsoft Edge blocking upload of log file is unrelated. I did delete the files on One Drive. I will post this to see if I can still post.

    0 comments
  4. techcoor 1,251 Reputation points
    2021-05-12T01:24:01.453+00:00

    Yes, name server 192.168.1.220 was removed but the problem continues.