DNS resolution fails on Ubuntu 12.10

[Adnane Belmadiaf]

Upstream bug report https://github.com/mitchellh/vagrant/pull/1176

[Impact]

Users of > 12.10 are unable to access the internet from their box due to a change in Ubuntu's DNS resolution ip address (127.0.0.1 to 127.0.1.1)

This makes vagrant completely unusable for users of 12.10 and raring.

[Test Case]

On a 12.10 or raring machine, setup a vagrant box based.

$ sudo apt-get install vagrant
$ vagrant box add myprecisevm http://files.vagrantup.com/precise32.box
$ vagrant init myprecisevm
$ vagrant up
$ vagrant ssh

Once logged in :
$ ping www.google.com

[Regression Potential]

Due to not currently being able to connect to the internet, I don't see any regression potential.

[Other Info]

Due to the fact that vagrant is unusable in 12.10, I'm recommending an SRU to make it usable.

[Stefano Rivera (stefanor)]

Uploaded quantal SRU, pending SRU team verification

[Launchpad Janitor (janitor)]

This bug was fixed in the package vagrant - 1.0.3-1ubuntu1

---------------
vagrant (1.0.3-1ubuntu1) raring; urgency=low

  * Detect Ubuntu's dns proxy (listening on 127.0.1.1) and disables
    internal dns proxying. [GH-1176]
    (LP: #1101914)
 -- Chris Johnston <email address hidden> Sun, 20 Jan 2013 13:13:13 -0500

[Adam Conrad (adconrad)]

Hello Adnane, or anyone else affected,

Accepted vagrant into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/vagrant/1.0.3-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Zygmunt Krynicki (zyga)]

It does not work for me on quantal with vagrant 1.0.3-1ubuntu1 and virtualbox 4.1.18-dfsg-1ubuntu1.1

I'm going to do some more testing but it seems borked so far.

[Zygmunt Krynicki (zyga)]

Ok, after some more testing I can confirm that this DOES NOT WORK.

The resolver inside the VM is set to 10.0.2.2. That is the gateway of the virtual NAT network. That address can be pinged properly but any nameserver resolution attempts fail. I've tried using dig but the request times out

$ dig @10.0.2.2 google.com

[Zygmunt Krynicki (zyga)]

This works with oracle virtualbox 4.1 package, presumably it carries the relevant bugfix already in the core. Still, not SRU-ready. I've finished my testing.

[Zygmunt Krynicki (zyga)]

To be precise, I tested it with the virtualbox-4.1 package version 4.1.24-82872~Ubuntu~quantal from the repo "deb http://download.virtualbox.org/virtualbox/debian quantal contrib"

[Chris Johnston (cjohnston)]

Virtualbox 4.1.18 has a bug as well.. https://www.virtualbox.org/ticket/10864

I'll look into this more later.

[Steve Langasek (vorlon)]

This package failed verification 10 months ago, and no update has been forthcoming. Package removed from quantal-proposed, and marking this bug 'wontfix'.