search

lmakarov / boot2docker-vagrant

[DEPRECATED] Boot2docker Vagrant box for optimized Docker and Docker Compose use on Mac and Windows
145 stars 41 forks source link

Reconsider VirtualBox DNS proxy on/off #49

Closed lmakarov closed 8 years ago

lmakarov commented 9 years ago

We are currently turning these off:

    # Disable VirtualBox DNS proxy as it may cause issues.
    # See https://github.com/docker/machine/pull/1069
    v.customize ['modifyvm', :id, '--natdnshostresolver1', 'off']
    v.customize ['modifyvm', :id, '--natdnsproxy1', 'off']

I ran into two use cases where it would be better to keep them on:

  1. Moving from one LAN to another will break DNS resolution

    B2D VM inherits the DNS server list from the host at boot. Moving into a different LAN (e.g. home <=> office) will mean a change of the network subnet and/or the DNS server IP address in most cases.

  2. I had a really weird issue on one Windows box with very poor network performance. I fixed it by switching natdnshostresolver1 and natdnsproxy1 ON.

At the minimum adding a note to the Troubleshooting docs about the switch would be good.

lmakarov commented 8 years ago

Revised this in https://github.com/blinkreaction/boot2docker-vagrant/commit/c9adb8d2325eb2c6d87e4ac36de26462aadec39f See the diff for details. Released in 1.5.0