Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

FQDN Now Resolves to Internal Switch IP on Host

$
0
0

I am having trouble with DNS resolution using my host's FQDN after creating a internal network for my VMs.

Previously, my FQDN (<computer-name>.<domain>) would resolve to my machine's external IP.  Since creating the internal switch, my FQDN now resolves to that switch's IP (192.168.0.1) when used by the host.  I am wondering where/why the creation of this internal switch is now overriding my FQDN resolution and how I can revert that to previous behavior.  I need the FQDN to resolve as the external IP so that I can use the services running in the VMs from the host itself.  I have tried forcing this resolution in my hosts file with <external IP> <fqdn> but that is also being ignore in lieu of the switch IP, and would also not be the desired solution since my external IP is not static.

All port forwarding and network behavior is working properly apart from the FQDN IP resolution on the host.

Any help would be appreciated!


Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>