Ticket #10864 (closed enhancement: fixed)
VirtualBox NAT-DNS fails if DNS service is listening on 127.0.1.1 -> fixed as of 17 Oct 2012 for 4.1, 4.2 and later
|Reported by:||rocko||Owned by:|
|Version:||VirtualBox 4.1.20||Keywords:||NAT DNS|
NAT-DNS does not work for guests running in virtualbox 4.2RC2 (I can't see that version in the version dropdown, btw, so I'm reporting against 4.1.20) in an Ubuntu 12.10 host with the default DNS setup, because virtualbox is sending DNS queries to the wrong address.
The host's /etc/resolv.conf contains
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1
The host's /etc/hosts contains:
127.0.0.1 localhost 127.0.1.1 sierra
And "sudo netstat -nl46p | grep :53" shows dnsmasq listening on 127.0.1.1:
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1971/dnsmasq udp 0 0 0.0.0.0:5353 0.0.0.0:* 1336/avahi-daemon: udp 0 0 0.0.0.0:53071 0.0.0.0:* 4493/VirtualBox udp 0 0 127.0.1.1:53 0.0.0.0:* 1971/dnsmasq udp6 0 0 :::5353 :::* 1336/avahi-daemon:
However, wireshark shows that VirtualBox is incorrectly trying to query 127.0.0.1 instead of 127.0.1.1.
A workaround is to manually force every VM to use the host's resolver with "VBoxManage modifyvm "VM name" --natdnshostresolver1 on" or to modify the guest's /etc/resolv.conf file with an external nameserver.
- Summary changed from VirtualBox NAT-DNS fails if DNS service is listening on 127.0.1.1 to VirtualBox NAT-DNS fails if DNS service is listening on 127.0.1.1 -> fixed as of 17 Oct 2012 for 4.1, 4.2 and later