README.md in landrush-0.12.0 vs README.md in landrush-0.13.0
- old
+ new
@@ -1,6 +1,6 @@
-# Landrush: DNS for Vagrant
+# Landrush: DNS for Vagrant [](https://travis-ci.org/phinze/landrush)
Simple DNS that's visible on both the guest and the host.
Spins up a small DNS server and redirects DNS traffic from your VMs to use it,
automatically registers/deregisters IP addresseses of guests as they come up
@@ -28,10 +28,20 @@
$ dig -p 10053 @localhost myhost.vagrant.dev
If you shut down your guest, the entries associated with it will be removed.
+### Dynamic entries
+
+Every time a VM is started, its IP address is automatically detected and a DNS record is created that maps the hostname to its IP.
+
+If for any reason the auto-detection detects no IP address or the wrong IP address, or you want to override it, you can do like so:
+
+ config.landrush.host_ip_address = '1.2.3.4'
+
+If you are using a multi-machine `Vagrantfile`, configure this inside each of your `config.vm.define` sections.
+
### Static entries
You can add static host entries to the DNS server in your `Vagrantfile` like so:
config.landrush.host 'myhost.example.com', '1.2.3.4'
@@ -61,9 +71,16 @@
config.landrush.upstream '10.1.3.10', 1001, :tcp
### Visibility on the Guest
Linux guests should automatically have their DNS traffic redirected via `iptables` rules to the Landrush DNS server. File an issue if this does not work for you.
+
+To disable this functionality:
+
+ config.landrush.guest_redirect_dns = false
+
+You may want to do this if you are already proxying all your DNS requests through your host (e.g. using VirtualBox's natdnshostresolver1 option) and you
+have DNS servers that you can easily set as upstreams in the daemon (e.g. DNS requests that go through the host's VPN connection).
### Visibility on the Host
If you're on an OS X host, we use a nice trick to unobtrusively add a secondary DNS server only for specific domains.