Ubuntu 12.04's use of networkmanager+dnsmasq breaks DNS for virtualbox VMs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In Ubuntu 12.04, the way NetworkManager defaults to using dnsmasq as a local forwarding resolver breaks VM configuration using VirtualBox.
In 12.04, VirtualBox's DHCP server provides the host's resolver's list of nameserver address to the guest. When the host's resolver is configured to communicate with a local nameserver via a loopback address, the guest will receive loopback IP addresses as nameserver addresses; but this does not work because there is no nameserver running on the guest. The guest's resolver should be configured to use the nameserver running on the *host*.
[Impact]
DNS doesn't work in guests
- when it uses the DNS server from the DHCP response and
- the host uses NetworkManager
[Test Case]
Running "host ubuntu.com" on the command line fails.
[Development Fix]
Fixed during Raring cycle.
[Stable Fix]
Is being fixed in 4.1.12-
4.1.18-
[Regression Potential]
We should verify that DNS in guests still works when the host
doesn't use networkmanager.
summary: |
- networkmanager+dnsmasq implementation seems to break DNS resolution for - virtualbox VMs + Ubuntu 12.04's use of networkmanager+dnsmasq breaks DNS for virtualbox + VMs |
description: | updated |
tags: | added: verification-done-quantal |
description: | updated |
I found https:/ /forums. virtualbox. org/viewtopic. php?f=7& t=50368 which gives some background.