DNS stopped working (NAT)

[Robin Green]

As I was browsing the web (going to fedoraproject.org, as it happens) DNS stopped working on the guest (Fedora Linux rawhide). I eventually thought to check on the host and it was working there, but still not working on the host. Networking on the guest was still working (my Bittorrent download continues to transfer data). I am using NAT networking.

I have used VirtualBox for months and this has never happened before. However, I did recently upgrade to 2.0.6 (OSE).

[Robin Green]

Oops... that should say "... but still not working on the guest".

I thought that overwriting the guest's /etc/resolv.conf with the one from the guest would work around the problem, but it had no effect.

[Robin Green]

Gah! With the one from the host, I meant to say.

[Ormtunga]

Had the same problem on my guest XP. Solved it by manually adding my DNS addresses to the network settings while keeping the IP and mask as DHCP.

[Robin Green]

I have not experienced this problem with recent VirtualBox versions.

[Michael Thayer]

I will close the ticket then. Please re-open if necessary.

[Josh Harding]

I've just experienced "DNS stopped working with NAT" with Ubuntu 9.04 Jaunty Guest running on VBox 3.06 r52128 on a WinXP SP3 host. Guest Additions installed.

From my host I can ping and resolve DNS look-ups no problems. With the guest I can ping any internet & LAN IP address no problems but CANNOT do any DNS resolution.

I've changed the Guest Ethernet Adapter types from PCnet-II, PCnet-Fast III, to Intel Desktop and back again.. each time with the same result - Guest can ping but not resolve DNS.

This is not a new install - both host & guest have been functioning correctly for almost a month. Only today has DNS stopped working correctly on the guest.

Until this bug is resolved, i've changes to bridged adapter. Would very much like to keep the guest firewalled from the host.

[vasily Levchenko]

Does it happen with Vbox 3.0.8? if yes please attach log file, ​pcap file and output of on host

# ipconfig /displaydns 

and

# cat /etc/resolve.conf

if it's sensible information please send information to me [vasily _dot_ levchenko _at_ Sun _dot_ COM].

[Frank Mehnert]

And please attach the VBox.log file for such a session (with NAT enabled please).

[vasily Levchenko]

Does

VBoxManage setextradata "Linux Guest"
      "VBoxInternal/Devices/pcnet/0/LUN#0/Config/UseHostResolver" 1

fixes issue for you, with 3.1b1?

[vasily Levchenko]

No response, closing. Please reopen if problem still persists.

[requiredfield]

I just hit this bug with the latest VirtualBox (4.3.2 r90405) running on an OS X 10.9 host and with Ubuntu and Windows 7 guests. As in the other posts above this happened without any obvious change that could have caused it after DNS had been working for months.

Changing the network adapter to bridged mode successfully works around it.

[vasily Levchenko]

Could you please attach the log file?