4.3.24 DNS for NAT Network stopped working

Discussions related to using VirtualBox on Windows hosts.
Post Reply
tkvb
Posts: 10
Joined: 3. Mar 2015, 06:33

4.3.24 DNS for NAT Network stopped working

Post by tkvb »

Host: Windows 8.1, VB 4.3.24
Guests: 2 Lubuntu 14.04.2, configured with NAT Network 10.0.5.0/24, static IPs, DNS 10.0.5.1, gateway 10.0.5.1
(the reason I want static IPs is so that the VMs can talk to each other and to have stable names for them in /etc/hosts; also, this is running on a laptop that moves between networks so I cannot do bridge as in some cases I can't get more than 1 IP)

With 4.3.22, I could set 10.0.5.1 as the DNS server in the guests and it would work fine, DNS requests would be proxied via the host resolver (I had set --natdnshostresolver1 on each VM). This stopped working in 4.3.24, 10.0.5.1 no longer responds to DNS requests, it just times out. I tried setting (again):

Code: Select all

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" modifyvm "Lubuntu" --natdnshostresolver1 on
but it does not help.
The only solution so far is to use a different DNS server (e.g. 8.8.8.8 ) in the guests, but that's less than ideal because some networks don't allow access to public DNS servers, internal servers must be used instead. The idea was to have VB proxy DNS requests all the time via the host resolver so I never have to worry about DNS settings in the guests (the host always gets them correctly via DHCP).

Update: I just learned that --natdnshostresolver1 does not apply to custom "NAT Network" type, only to the default NAT type. See this comment.
Last edited by tkvb on 5. Mar 2015, 16:25, edited 1 time in total.
da4an1qu1
Posts: 3
Joined: 5. Mar 2015, 08:34

Re: 4.3.24 DNS for NAT Network stopped working

Post by da4an1qu1 »

I can confirm seeing this behaviour. If I move from network to network, the NAT is still announcing the DNS from the first network I started the VM under.
fangorn
Posts: 1
Joined: 5. Mar 2015, 12:12

Re: 4.3.24 DNS for NAT Network stopped working

Post by fangorn »

I confirm the same issue. But in my case poweroff/poweron the client machine does not work - some of virtual machines (guests with Windows 7) completely do not accept DNS server address via dhcp, so every time I move my laptop from office network and back I need to manually set external/internal DNS server address.
tkvb
Posts: 10
Joined: 3. Mar 2015, 06:33

Re: 4.3.24 DNS for NAT Network stopped working

Post by tkvb »

I opened this ticket, if you want to add your comments to it:
https://www.virtualbox.org/ticket/13915

And it seems MacOS has the same problem:
https://www.virtualbox.org/ticket/13918
Post Reply