none
Win 10 failing to get responses from 2012 R2 DNS RRS feed

  • Question

  • I have two AD DNS servers: dns1.example.local and dns2.example.local.  Dns1 is running Windows Server 2016, while Dns2 is running Server 2012 R2.

    My Windows 10 (1809) workstation is able to make DNS lookups from the dns1 server:

    Non-authoritative answer:
    Name:    purple.com
    Addresses:  2606:4700:10::6814:37eb
              2606:4700:10::6814:38eb
              104.20.55.235
              104.20.56.235

    However, when I try the same query against dns2 from my Win 10 workstation:

    *** dns2.example.local can't find purple.com: No response from server

    But if I try the same query for purple.com against dns2 from itself, another Server 2012 R2 machine or even a MacOS 10.14.1 client, it will successfully return the results.  Unfortunately, I don't have an exact time frame as to when this issue began showing up as dns1 is my primary server on my workstation.  I just received my first user complaint today (Wednesday).  I just did the March round of patches on this server over the weekend.

    I also had one of my co-workers try the query from her Windows 10 (1803) machine, but it also gets no response from dns2.  I checked around and found another workstation running Windows 10 (1709) and found it can successfully query dns2.

    Wednesday, March 27, 2019 10:19 PM

Answers

  • Hi,

    • Please force NSLookup to use the IPv4 address on the clients.

           Nslookup

           >server 192.168.88.12

    • Please check if the DNS server is listening on the IPv6 interface.

    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 Castaway Kid Monday, April 1, 2019 3:51 PM
    Monday, April 1, 2019 6:51 AM
    Moderator
  • Ok, that did the trick.  Forcing NSLookup to use the IPv4 address resolved the "no response" error.  I then configured the server to only listen to the IPv4 address and restarted the DNS service.  I was then able to have NSLookup use the server name instead of forcing the explicit IPv4 address.
    • Marked as answer by Castaway Kid Monday, April 1, 2019 3:55 PM
    Monday, April 1, 2019 3:54 PM

All replies

  • Hi,

    Please check the preferred DNS server of network adapter properties on clients.

    If the DNS server don't work, it should return time out not no response.

    So I suspect that someone has changed the DNS address on the clients.

    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

    Thursday, March 28, 2019 6:01 AM
    Moderator
  • I've verified the DNS settings are correct on the clients.  Here is a more complete output from my command prompt:

    PS Z:\> nslookup
    Default Server:  dns1.example.local
    Address:  192.168.88.15
    > purple.com
    Server:  dns1.example.local
    Address:  192.168.88.15
    Non-authoritative answer:
    Name:    purple.com
    Addresses:  2606:4700:10::6814:37eb
              2606:4700:10::6814:38eb
              104.20.55.235
              104.20.56.235
    > server dns2
    Default Server:  dns2.example.local
    Addresses:  2002:c096:580c::c0a8:580c
              192.168.88.12
    > purple.com
    Server:  dns2.example.local
    Addresses:  2002:c096:580c::c0a8:580c
              192.168.88.12
    *** dns2.example.local can't find purple.com: No response from server

    Thursday, March 28, 2019 6:00 PM
  • Hi,

    Form the result of nslookup, I found that there are two IP addresses of dns2.example.local.

    Could you ping the IPv6 address 2002:c096:580c::c0a8:580c from your clients?

    As a test, please disable ipv6 address.

    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

    Friday, March 29, 2019 9:10 AM
    Moderator
  • Trying to ping the IPv6 address results in a "transmit failed: General Failure" message.  I get the same results when I disable IPv6 on my client's NIC.  

    As for the servers, it is my understanding that Microsoft strongly recommends not disabling the IPv6 protocol.  Interesting that both of the servers have it enabled, but only the 2012 R2 server reports its IPv6 address in the nslookup tool.

    Friday, March 29, 2019 2:05 PM
  • Hi,

    • Please force NSLookup to use the IPv4 address on the clients.

           Nslookup

           >server 192.168.88.12

    • Please check if the DNS server is listening on the IPv6 interface.

    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 Castaway Kid Monday, April 1, 2019 3:51 PM
    Monday, April 1, 2019 6:51 AM
    Moderator
  • Ok, that did the trick.  Forcing NSLookup to use the IPv4 address resolved the "no response" error.  I then configured the server to only listen to the IPv4 address and restarted the DNS service.  I was then able to have NSLookup use the server name instead of forcing the explicit IPv4 address.
    • Marked as answer by Castaway Kid Monday, April 1, 2019 3:55 PM
    Monday, April 1, 2019 3:54 PM
  • Hi,

    I am glad to hear that your issue was successfully resolved.

    If there is anything else we can do for you, please feel free to post in the forum.

    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

    Tuesday, April 2, 2019 1:01 AM
    Moderator