Skip to content

Instantly share code, notes, and snippets.

@mitchellh
Created October 11, 2011 01:30
Show Gist options
  • Star 43 You must be signed in to star a gist
  • Fork 10 You must be signed in to fork a gist
  • Save mitchellh/1277049 to your computer and use it in GitHub Desktop.
Save mitchellh/1277049 to your computer and use it in GitHub Desktop.
Configure Vagrant VM to use Host DNS for VPN
Vagrant::Config.run do |config|
# ...
config.vm.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
end
@abtris
Copy link

abtris commented Feb 17, 2012

how it possiblem in new vagrant configure this "config.vm.customize now takes an array of arguments" ? Thx

@fingermark
Copy link

Same question

@mitchellh
Copy link
Author

I updated the gist to be accurate again :)

@jbrown
Copy link

jbrown commented Sep 14, 2012

Is this still accurate for the latest version of Vagrant? Doesn't seem to work for me...

@Alexandervn
Copy link

Thanks a lot!

Worked perfect for me on Ubuntu 12.10 host with Ubuntu 12.04 guest.

@marcgibbons
Copy link

Very nice

@patcon
Copy link

patcon commented Jan 29, 2013

Worked perfect on ubuntu lucid

@JerryPreissler
Copy link

Worked with the Lucid Box for Vagrant running on Quantal. Thanks a lot.

@adamdicarlo
Copy link

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...

@ichilton
Copy link

ichilton commented Mar 4, 2013

Does this have any performance impact?

@apinstein
Copy link

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?

@eikonomega
Copy link

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

@awsiv
Copy link

awsiv commented Jun 3, 2013

@eikonomega: thanks!

This also works with v1.2

@foton
Copy link

foton commented Jan 31, 2014

Yes, this make it work on Ubuntu 13.10.

@danmayer
Copy link

danmayer commented Feb 5, 2014

This fixes DNS lookup but host is still unreachable from within the VM, anyone have a tip for that?

@AnalogJ
Copy link

AnalogJ commented Jul 7, 2014

Does this fix work for Vagrant + VMWare + VPN's as well?

@mattgray
Copy link

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

@rafaelrp
Copy link

Worked in homestead/vagrant 1.6.3 with Ubuntu 14.10

=]

@ducminhvu
Copy link

work like a charm thanks

@GTP95
Copy link

GTP95 commented Jul 2, 2021

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
    `

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment