I have a issues with a VMware hosted Server 2019 that is used by a client for running legacy applications. It is also syncing to Office 365 Azure AD.
Its an all in one AD and RDS server. We have a weird issues where where every day or two, its DNS server stops being able to resolved external addresses. The DNS is using external relay servers
Restarting the DNS service does not resolve the problem, but rebooting windows does resolve it. disabling and re-enabling the network interface also resolves it for a day or two. Even when the DNS is failing, I can ping out and routing seems to be fine. The only network interface is using 127.0.0.1 as its preferred DNS (the server is sitting behind a hosted firewall with VPN service).
Looking at the DNS server log, I see the following errors come up when the DNS fails.
- 407 - The DNS server could not bind a User Datagram Protocol (UDP) socket to 192.168.1.1. The event data is the error code. Restart the DNS server or reboot your computer.
- 408 - The DNS server could not open socket for address 192.168.1.1.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.
- 404 - The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 192.168.1.1. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.
What I have tried so far,
- I have reinstalled VMware tools and VMXnet adaptor driver
- I have switched it to the E1000 interface type
- I have checked for disabled/old interfaces that may use the same 192.168.1.1 IP
- in device manager (hidden devices)
- in registry
It really baffles me that it works fine for hour/days at random and then just stops. At this point I am out of ideas, any tips?