Hello,

A customer’s domain server has stopped responding to DNS queries.

The servers’ windows firewall shows port 53 for TCP & UDP as allowed and when I run " netstat -a -n -p udp " from the command prompt on the server in question it shows that it is listening on UDP port 53.

However if I try and telnet to the server IP from a PC on the same subnet to check if port 53 is listening I get no reply. Similarly if I set a domain PC to use the server for DNS and do an nslookup command I get the “unknown server” message and subsequently timeouts on any lookups.

From the server itself however it can resolve DNS names (internal & external) .

To get them basic service I have just added in Google DNS in static DNS entries on the PCs (only 15 so not a big deal).

The server is a VM and they have a backup image so it can be restored but I’m wondering if there is something simple that I am overlooking ?

Cheers

Gavin

12 Spice ups

How is the DC configured for DNS?

Do the clients point to the DC for DNS, and only this?

Can a client device ping the DC by name or DNS?

Is the DNS service started?

While it should be, can you check the firewall profile on the DC is set to domain (and/or reboot it if you have not yet)

Make sure the NIC had the correct NLA setup for domain and not public or internet

3 Spice ups

Is the DNS service running? Anything in the event logs?

2 Spice ups

^This happens quite a bit after updates with Sever 2016 and Windows 10. I also do not recommend browsing the Internet on a DC.

Are you also having problems with users logging to the workstations?

You could try restarting the network location awareness service. It may not recognise the nic as being on a domain.