[Pkg-virtualbox-devel] Bug#464574: Bug#464574: Bug#464574: virtualbox-ose: No network in

[Emilio Jesús Gallego Arias]

retitle 464574 If first line of /etc/resolv.conf is invalid, dns doesn't work in the guests
severity 464574 minor

thanks

Hi,

"Torsten Werner" <mail.twerner at googlemail.com> writes:

> On Feb 9, 2008 11:23 AM, Michael Meskes <meskes at debian.org> wrote:
> ping cannot work with NAT because virtualbox would have to run as root.

Ok, I understood the NAT used in virtualbox and found the problem,
thanks for the hint. (I was incorrectly relying on ping)

The problem is that in my resolv.conf the first line was invalid, as in
the upgrade bind9 got uninstalled. My resolv.conf was like

$ cat /etc/resolv.conf
domain ls.fi.upm.es
nameserver 127.0.0.1
nameserver $exteranl

It seems that virtualbox NAT can only use the first line of resolv.conf
for dns servers, thus dns started to fail in the guests.

I reinstalled my caching dns server:

$ host babel.ls.fi.upm.es localhost
Using domain server:
Name: localhost
Address: 127.0.0.1#53
babel.ls.fi.upm.es has address 138.100.12.136

and the setup wasn't working, but I figure this is because bind by
default listens to local connections. Once I tried setting up a correct
first nameserver line, the virtual machines are working again.

Thanks for your help,

Emilio