none
DNS server cannot resolved itself, but can serve other computers RRS feed

  • Question

  • It happends 2 times that our DNS server (windows 2019 standard) somehow cannot resolved DNS record itself suddenly, but it can serve other computer without issue, no error on event viewer whatsoever.

    - We try to restart dnsclient service, but its not possible with windows server 2019
    - ipconfig /flushdns doesnt work
    - we dont have ipv6 on that server configure
    - no error or warning on event viewer

    Our environement

    - domain with 3 DC 
    - seperate Windows 2019 with DNS role (the one which has the problem)

    any idea how to resolved this?

    Wednesday, June 12, 2019 8:36 AM

Answers

  • Hi,

    There is a known issue that event 7600 in the Domain Name System (DNS) server event log to contain an unreadable server name.

    Please refer to the link below:

    https://support.microsoft.com/en-sg/help/4497934  

    I would suggest you update to the latest version.

    Best regards,

    Travis


    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 Ayaaaa Wednesday, June 19, 2019 7:14 AM
    Thursday, June 13, 2019 7:07 AM
    Moderator

All replies

  • Hi,

    Did you create PTR record for DNS server?

    What is the result of Nslookup?

    Best regards,

    Travis


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

    Wednesday, June 12, 2019 9:19 AM
    Moderator
  • Dear Travis,

    PTR record exist

    When the problem occurs at the time, nslookup on the dns server itself gave server unknown

    but the clients computer can resolving just fine on the server itself

    Wednesday, June 12, 2019 9:25 AM
  • Hi,

    How did you set DNS server addresses on NIC?

    Please set other DC(DNS) address as preferred DNS server and set local IP address (not 127.0.0.1) as alternate DNS server.

    Meanwhile, check interfaces the DNS listens on.

    Best regards,

    Travis


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

    Wednesday, June 12, 2019 9:34 AM
    Moderator
  • Hi,

    In your IP V4 setup, how many DNS servers are listed?

    In DNS configuration, what are your forwarders, or are you using root hints?

    Regards,

    Leslie

    Wednesday, June 12, 2019 9:39 AM
  • Hey Travis,

    the preferred DNS is the ip address of the server itself, as its the master of its own zone, alternate dns is an DC DNS server,

    and interfaces DNS listens on all ip address as your screenshot

    Wednesday, June 12, 2019 10:08 AM
  • Dear Leslie,

    in my ipv4 setup, 2 dns server are listed

    in dns configuration, no forwarders, just root hints

    Wednesday, June 12, 2019 10:09 AM
  • Hi,

    There is a known issue that event 7600 in the Domain Name System (DNS) server event log to contain an unreadable server name.

    Please refer to the link below:

    https://support.microsoft.com/en-sg/help/4497934  

    I would suggest you update to the latest version.

    Best regards,

    Travis


    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 Ayaaaa Wednesday, June 19, 2019 7:14 AM
    Thursday, June 13, 2019 7:07 AM
    Moderator
  • Hi,

    Just checking in to see if the information provided was helpful.

    Please let us know if you would like further assistance.

    Best Regards,

    Travis

    <o:p></o:p>


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

    Wednesday, June 19, 2019 7:02 AM
    Moderator
  • Hello Travis

    i have installed the patch yesterday. I hope the issue wont reappear, i will close the case for now and reopen if the issue is not solved, thax

    Wednesday, June 19, 2019 7:14 AM