Sunday, September 6, 2020

Can't Resolve VM from Domain

Hello Everyone,

Networking isn't my strong suit, so forgive me if this is trivial.

I have one virtual machine that I am having issues with. I can't RDP into it, its not accepting Group Policy updates, and won't be resolved via DNS. I think I've narrowed it down to a DNS issue, but I am not sure.

I have three computers. One is a Windows Server 2019 VM (192.168.162.10), a physical laptop (192.168.162.228), and a VM (192.168.162.151). The VM is the one I am having trouble with.

I can ping all the machines via IP and hostname.

NSLookup is more spotty. If I try to resolve the VM from the physical machine, I get nothing - by IP or hostname. From the VM, I get an incorrect IP (192.168.162.170), which isn't present on the network. If I use its actual IP, or its hostname, I get "Non-Existent Domain". From the VM, I can resolve the IP of the server by hostname, but not by IP.

I've tried the troubleshooting found here : http://techgenix.com/10-ways-troubleshoot-dns-resolution-issues/ and nothing fixed it - verifying DNS server IP, pinging, verifying DNS settings (the VM points to the Windows Server and then to the ISP DNS server), verifying DNS suffix, /release & /renew, Clear DNS server cache, restart DNS service, etc.

Everything looks correct. The VM is part of the domain (the domain is listed in the Primary DNS Suffix). However, my ISP is listed in the "Connection-specific DNS Suffix" under the Ethernet adapter in ipconfig /all. Similarly, it lists my ISP as the in Settings > Network & Internet > Ethernet > <Domain> > Primary DNS Suffix.

So, I am out of ideas. If anyone has some advice or guidance, i'd be grateful.



No comments:

Post a Comment