-
-
Save mitchellh/1277049 to your computer and use it in GitHub Desktop.
| Vagrant::Config.run do |config| | |
| # ... | |
| config.vm.customize ["modifyvm", :id, "--natdnshostresolver1", "on"] | |
| end |
I updated the gist to be accurate again :)
Is this still accurate for the latest version of Vagrant? Doesn't seem to work for me...
Thanks a lot!
Worked perfect for me on Ubuntu 12.10 host with Ubuntu 12.04 guest.
Very nice
Worked perfect on ubuntu lucid
Worked with the Lucid Box for Vagrant running on Quantal. Thanks a lot.
Hmm, what does this solve exactly? My issue is that my vagrant NFS shares don't work when my host is logged into a VPN because it captures all network traffic...
Does this have any performance impact?
after I do this and halt/up, vagrant no longer works. The machine will still boot, and the DNS is fast again, but there are no vagrant shared folders and provision fails due to nothing in /vagrant.
Any idea?
I found that this syntax didn't work as expected on V1.1.5
Here the replacement that worked for me.
config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
end
@eikonomega: thanks!
This also works with v1.2
Yes, this make it work on Ubuntu 13.10.
This fixes DNS lookup but host is still unreachable from within the VM, anyone have a tip for that?
Does this fix work for Vagrant + VMWare + VPN's as well?
Hi, I had the same problem trying to configure host DNS resolver so that I can resolve addresses from a private DNS server over a VPN, except using Test Kitchen instead of plain Vagrant. This gist configures the the test kitchen vagrant driver in the same way as above gist, except in the .kitchen.yaml syntax : https://gist.github.com/mattgray/0a72e8d61a5ca115c406
Worked in homestead/vagrant 1.6.3 with Ubuntu 14.10
=]
work like a charm thanks
Unfortunately, this seems to not be working anymore, got the following error while trying to destroy my previous VM:
`There are errors in the configuration of this machine. Please fix
the following errors and try again:
vm:
- The following settings shouldn't exist: customize
`
Same question