Why does DNS installed at Domain Control report an error using nslookup?

Question

domain controller

domain controller

domain controller

Why does DNS installed at Domain Control report an error using nslookup?

Why shows “DNS request timed out"?

Why Default Server shows "UnKnown"?

But member DNS, using nslookup shows normal

Answer 1

Two things

1. add 192.168.9.191 listed for DNS primary, move loopback (127.0.0.1) to secondary
2. try the regedit here to Prefer IPv4 over IPv6 https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows

--please don't forget to close up the thread here by marking answer if the reply is helpful--

Answer 2

What's the result of

ipconfig /all

Answer 3

Could you clarify which domain controller is experiencing the issue, is the affected DC a Primary Domain Controller?

Also, please check if the NIC has a manually configured DNS Server.

If you're not a fan of CLI, you can navigate to:

Control Panel -> Network and Internet -> Network and Sharing Center

At the left side select the option "Change adapter settings"

This will show you the network adapters on the server.

Double click on the NIC and select Properties, or right click and then select Properties.

Click on the Internet Protocol Version 4, and check if the IPv4 address is set, and below the IPv4 config you'll see two options:

Obtain DNS server address automatically (should be grayed out, if the IPv4 address is set to a static one)

Use the following DNS Server addresses (This show be selected, kindly check if the Preferred DNS Server (i.e. Primary DNS Server for lookup) is set to 127.0.0.1)

If your company uses IPv6 internally, then do the same thing, on the IPv6 protocol, the preferred DNS server should be ::1 (i.e. the representation of localhost loopback-address in IPv6)

It's important to note that it's not a bad idea if you try to open the DNS Snap-In (DNS Manager) right click on the local server and select Properties, from there the first screen you'll see is Interfaces tab, you could try and see if everything's correct, and if you don't hesitate try to enable the server to listen on All IP addresses, if your environment allows that.

If the issue still persist, please write me an email to continue up the topic: krasimir.rangelov@hotmail.com

Answer 4

how can a domain controller not use IPv6?

IPv4 is not a problem. The better option is as I mentioned above though.

--please don't forget to close up the thread here by marking answer if the reply is helpful--

Answer 5

Yeah, rebooted domain control.

The simplest solution for your test environment may be to uncheck IPv6 on the connection properties. Nothing gets uninstalled, it is simply turned off for this connection.

--please don't forget to close up the thread here by marking answer if the reply is helpful--