This is similar to this question, but my problems are more severe.
I cannot resolve any host names inside my precise64-client set up by Vagrant.
vagrant@gitclients-vbox:~$ nslookup google.com
;; connection timed out; no servers could be reached
The vagrant machine uses 10.0.2.3 as a name-server:
vagrant@gitclients-vbox:~$ cat /etc/resolv.conf
nameserver 10.0.2.3
But this IP is not configured as a name-server, I cannot ping it and it does not resolve host-names.
The interfaces of the client are configured as:
- eth0: 10.0.2.15
- eth1: 192.168.1.100
On my host machine, it works perfectly:
ced@ced:~$ nslookup google.com
Server: 127.0.1.1
Address: 127.0.1.1#53
Non-authoritative answer:
Name: google.com
Address: 173.194.35.38
..
Here's the vagrant file:
Vagrant::Config.run do |config|
config.vm.host_name = "gitclients-vbox"
config.vm.box = "precise64"
config.vm.box_url = "http://files.vagrantup.com/precise64.box"
config.vm.network :hostonly, "192.168.1.100"
config.vm.provision :puppet do |puppet|
puppet.manifests_path = "puppet/manifests"
puppet.manifest_file = "nodes.pp"
end
end
Also, on my colleagues work-station, it works though. Here is the version comparison:
- My host: Ubuntu Desktop 12.10, VirtualBox 4.1.18, Vagrant 1.0.3
- Colleague: Ubuntu Desktop 12.04, VirtualBox 4.1.12, Vagrant 1.0.1
