README.md in landrush-1.1.0.beta.1 vs README.md in landrush-1.1.0.beta.2

- old
+ new

@@ -26,10 +26,11 @@ - [Windows](#windows) - [Other Devices \(phone\)](#other-devices-phone) - [Additional CLI commands](#additional-cli-commands) - [Miscellaneous Tricks and Tips](#miscellaneous-tricks-and-tips) - [How to avoid providing sudo password on OS X](#how-to-avoid-providing-sudo-password-on-os-x) + - [Guest is unable to access the Internet](#guest-is-unable-to-access-the-internet) - [Development](#development) - [Help Out!](#help-out) <!-- /MarkdownTOC --> @@ -144,12 +145,13 @@ work for anything. <a name="unmatched-queries"></a> ### Unmatched Queries -Any DNS queries that do not match will be passed through to an upstream DNS server, so this will be -able to serve as the one-stop shop for your guests' DNS needs. +Any DNS queries that do not match any of Landrush'es configuration data, will be passed +through to an upstream DNS server. Per default Landrush uses Google's DNS server with the +IP _8.8.8.8_. If you would like to configure your own upstream servers, add upstream entries to your `Vagrantfile` like so: config.landrush.upstream '10.1.1.10' @@ -175,12 +177,17 @@ <a name="visibility-on-the-host"></a> ### Visibility on the Host Visibility on the host means that the hostname of the VMs can be resolved on the host's DNS system. -Depending on the OS this might require some manual configuration. +Landrush will attempt an automatic configuration of the host, but depending on the OS, manual +configuration might be required as well. +To disable this functionality: + + config.landrush.host_redirect_dns = false + <a name="os-x"></a> #### OS X If you're on an OS X host, we use a nice trick to unobtrusively add a secondary DNS server only for specific domains. Landrush adds automatically during startup a file into `/etc/resolver` @@ -188,12 +195,15 @@ (Check out `man 5 resolver` on your Mac OS X host for more information on this file's syntax.) <a name="linux"></a> #### Linux -Though it's not automatically set up by Landrush, similar behavior can be achieved on Linux hosts -with `dnsmasq`. You can integrate Landrush with `dnsmasq` on Ubuntu like so (tested on Ubuntu 13.10): +Landrush tries to achieve the same behavior on Linux hosts using +`dnsmasq`. For some Linux distributions this happens automatically (you might +have to provide your _sudo_ password). If Landrush does not know how to install and +start `dnsmasq` on your favorite Linux distribution, you can adjust the following +example from Ubuntu: sudo apt-get install -y resolvconf dnsmasq sudo sh -c 'echo "server=/vagrant.test/127.0.0.1#10053" > /etc/dnsmasq.d/vagrant-landrush' sudo service dnsmasq restart @@ -305,9 +315,23 @@ Cmnd_Alias VAGRANT_LANDRUSH_HOST_MKDIR = /bin/mkdir /etc/resolver/* Cmnd_Alias VAGRANT_LANDRUSH_HOST_CP = /bin/cp /*/vagrant_landrush_host_config* /etc/resolver/* Cmnd_Alias VAGRANT_LANDRUSH_HOST_CHMOD = /bin/chmod 644 /etc/resolver/* %admin ALL=(ALL) NOPASSWD: VAGRANT_LANDRUSH_HOST_MKDIR, VAGRANT_LANDRUSH_HOST_CP, VAGRANT_LANDRUSH_HOST_CHMOD # End Landrush config + +<a name="guest-is-unable-to-access-the-internet"></a> +### Guest is unable to access the Internet + +In some network configuration the access to outside DNS servers is restricted +(firewalls, VPN, etc). Since unmatched DNS queries are per default passed through to +Google's DNS servers, this can lead to the fact that the guest cannot access anything +in the outside world. +If you are having problem with the guest's DNS, verify that you can access Google's +DNS server under _8.8.8.8_. If it does not work, you will need to set a custom +upstream DNS server. Check your network configuration on the host or ask your network +administrator about the right DNS server address to use. You can set the custom +DNS server via the _config.landrush.upstream_ option (see section about +[unmatched queries](#unmatched-queries)). <a name="development"></a> ## Development The following should get you started to develop on the Landrush code base. As a prerequisite you