Ticket #421 (closed defect: duplicate)
DNS not working
Reported by: | rozelak | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 1.4.0 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Hallo,
I just wanted to try VirtualBox, but I realized that dns is probably broken in 1.4.0 binary version (installed through gentoo portage), with default NAT network setting.
When I try to connect e.g. to 'www.google.com' in internet explorer (WindowsXP proffesional), it fails everytime. However, setting address '64.233.183.99' to IE works perfectly! The same situation repeats for any internet page. I have also tried to ping the gate for virtualized Windows (ping 10.0.2.2), everthing works erfectly, but the ping of dns server (ping 10.0.2.3) ends with 'Request timed out' message.
Due to the fact that net is available through addresses, I gues that the problem is in inbuild DNS. Naturally, net works perfectly from native linux.
Regards, Roz.
Change History
comment:2 Changed 16 years ago by sandervl73
- Status changed from new to closed
- Resolution set to fixed
No reply for 5 months. Closing.
comment:3 Changed 15 years ago by Electrum
- Status changed from closed to reopened
- Resolution fixed deleted
The host is Linux and uses dnsmasq for DNS caching. This could be fixed by proxying DNS or allowing DNS configuration. Note that this setup works with QEMU's NAT, so QEMU must handle it differently.
host$ cat /etc/resolv.conf search internal nameserver 127.0.0.1
Log:
00:11:45.951 NAT: passing domain name internal 00:11:45.951 NAT: DNS address: 127.0.0.1 ... 00:12:10.224 NAT: DNS address: 127.0.0.1
comment:5 Changed 15 years ago by Electrum
A quick summary: The host OS has 127.0.0.1 set for the DNS server in /etc/resolv.conf. VirtualBox passes 127.0.0.1 as the DNS server to the guest OS. This obviously incorrect as 127.0.0.1 is the loopback address.
Can you please attach a log file for a VM where DNS doesn't work? The log file shows what DNS server our built-in DNS forwarder uses. It's most likely that it uses the wrong one. VirtualBox gets the host's DNS configuration from /etc/resolv.conf.
And the issue with pinging the built-in DNS "server" is normal. See the manual about pinging in NAT network configuration.