Ticket #4484 (closed defect: duplicate)
Create DNS proxy using Host resolving API
|Reported by:||rfm||Owned by:|
|Version:||VirtualBox 3.0.2||Keywords:||DNS, DHCP|
After upgrading from VirtualBox 2.2.x to 3.0.2 on an Ubuntu 9.04 host, the WinXP guest using NAT networking and DHCP no longer could resolve DNS names. Checking ipconfig showed the DNS server list was empty. Since my host runs a caching/forwarding BIND server, I had left /etc/resolv.conf empty (no "nameserver" entries), depending on the default resolver library behavior of using the loopback address if nothing else is specified. After changing /etc/resolv.conf to contain nameserver entries for 127.0.0.1 and the servers I normally forward to, VBox DHCP correctly fed the NAT gateway address and the forwarding servers to the guest, and everything was fine.
This host config did work prior to upgrading to 3.0.2; I suspect there used to be a special case to handle no nameserver entries in /etc/resolv.conf that somehow got broken by some other change.
- Summary changed from DHCP gives no DNS server if /etc/resolv.conf is empty to Create DNS proxy using Host resolving API