Paul Hinze

It's entirely possible that `resolve.conf` ends up being a better solution for this. I found iptables to be easier to implement at. Its safe to run late in the stack,...

Thanks for looking into this! :telescope: Ah yes, that may be because (IIRC) vmware's dns runs through the host's dns stack, and we have things properly configured for OSX hosts....

@highb I just thought of something, are you looking at the NAT table? ``` bash sudo iptables -nvL -t nat ```

> reload it seems that the iptables are messed up on reload, but the regular up / down cycle is great however. So that pretty much sucks because we use...

> not related however, is there any way to map the host machine to a hostname as well? Interesting idea! I'd recommend a fresh issue for that discussion. :mega:

This is fixed for reload in #101 - still not handled for guest-initiated reboot, so leaving open for that.

Thanks for the detailed reporting! And sorry for the trouble with the config... it definitely seems broken from your investigation. I'll dig into this and see if I can reproduce.

So I'm able to set OpenDNS servers using the config option like so: ``` ruby Vagrant.configure("2") do |config| config.vm.box = "hashicorp/precise64" config.vm.hostname = "issue78.vagrant.dev" config.landrush.enabled = true config.landrush.upstream '208.67.222.222' end...

Hi @karmelak sorry I missed the notification for this issue! :see_no_evil: Would you mind letting me know the host/guest you were trying for this if you can remember?

Will do - is the box you used for debian wheezy one of the ones up on http://www.vagrantbox.es/?