natdnshostresolver1 not working when switching networks.

[snowboardguy711]

Using Virtualbox 5.0.16.
Slackware Linux Hosts.
Oracle Enterprise Linux 6.5 guest. Virtualbox Guest additions installed.

I have a laptop that i use at work, at home, and on the train when I commute. I have my vm's setup to use nat. The guests are assigned IP's using DHCP. I changed the default network to mimic my company's ip range
by setting
VBoxManage modifyvm "Utility-Box" --natnet1 "172.22.79/24

I also set nat to use the host resolver.
VBoxManage modifyvm "Utility-Box" --natdnshostresolver1
This had the effect of setting /etc/resolv.conf to the following value when the node is booted.
options timeout:1
options attempts:2
; generated by /sbin/dhclient-script
nameserver 172.22.79.3

The problem occurs if i switch my laptop from one wifi network to another on the host. When I switch to a different network on the host, the guest can no longer resolve dns. I can ping IPs in the network that I moved to but a dns request will cause the host to freeze up and become unresponsive. I thought the natdnshostresolver1 was supposed to fix this issue. Has anyone else had problems when you move between networks on the hosts? Thanks any help would be appreciated.

Please let me know if you need me to provide any logs.

[Perryg]

Have you tried adding a fixed name server like 8.8.8.8 or what ever your NS of choice is?

[snowboardguy711]

Well i'd prefer not to use a public dns server. I will also be using these nodes when i'm connected to my corporate network and will need to use DNS inside my company's to access hosts on our network.

[Perryg]

The great thing about DNS servers and adding but not replacing them is you can set the metric and have them both working with one higher than the other so it tries it first and then the second one if that fails, but the call is always yours.

[snowboardguy711]

Would you know how to open a bug for this issue? I do not know if I have access.