Bug#464574: [Pkg-virtualbox-devel] Bug#464574: Bug#464574: virtualbox-ose: No network in
Michael Meskes [EMAIL PROTECTED] writes: I take it you're talking about the first nameserver line, right? Yes. I just added nameserver 1.1.1.1 to my resolv.conf and while becoming slower the system still works as advertised. I tried the same (first line a bad nameserver = 1.1.1.1) and 2nd one a good (non-local) one and the problem persists. Could it be that your local DNS server answered the queries without giving the IP number? I have ruled out this possibility. I'm running up to date Debian Lenny. Let me know what can I do to help to debug this. Regards and thanks, Emilio pgpGs9ZuqNp68.pgp Description: PGP signature
Bug#464574: [Pkg-virtualbox-devel] Bug#464574: Bug#464574: virtualbox-ose: No network in
On Sat, Feb 09, 2008 at 05:59:06PM +0100, Emilio Jesús Gallego Arias wrote: The problem is that in my resolv.conf the first line was invalid, as in I take it you're talking about the first nameserver line, right? I just added nameserver 1.1.1.1 to my resolv.conf and while becoming slower the system still works as advertised. Could it be that your local DNS server answered the queries without giving the IP number? Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
Bug#464574: [Pkg-virtualbox-devel] Bug#464574: Bug#464574: virtualbox-ose: No network in
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 [EMAIL PROTECTED] writes: On Feb 9, 2008 11:23 AM, Michael Meskes [EMAIL PROTECTED] 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
