vagrant-dns

vagrant-dns allows you to configure a dns-server managing a development subdomain. It works much like pow, but manages Vagrant machines.

Installation

If you use the gem version of Vagrant, use:

$ gem install vagrant-dns

otherwise, use:

$ vagrant gem install vagrant-dns

Usage

In addition to your networking config, configure a toplevel domain and a host_name for your machine. Optionally, configure a set of free matching patterns. Global configuration options can be given through the VagrantDNS::Config object:

Vagrant::Config.run do |config|
  #...

  config.dns.tld = "dev"

  config.vm.host_name = "machine"

  config.dns.patterns = [/^.*mysite.dev$/, /^.*myothersite.dev$/]

  config.vm.network :hostonly, "33.33.33.60"
end

# optional
VagrantDNS::Config.logger = Logger.new("dns.log")

Then, register the DNS server as a resolver. RVM users must use rvmsudo instead of sudo:

$ sudo vagrant dns --install

On OS X, this will create a file /etc/resolver/dev, which tells OS X to resolve the TLD .dev by using the nameserver given in this file. You will have to rerun --install every time a tld is added.

You can delete this file by running:

$ sudo vagrant dns --uninstall

Then, run the DNS server:

$ vagrant dns --start

And test it:

$ dig @localhost -p 5300 test.machine.dev

You can now reach the server under the given domain.

Finally, stop the server using:

$ vagrant dns --stop

The DNS server will start automatically once the first VM is started.

VM options

• vm.dns.tld: Set the tld for the given virtual machine. No default.
• vm.dns.tlds: Set multiple tlds. Default: [tld]
• vm.dns.patterns: A list of domain patterns to match. Defaults to [/^.*{host_name}.{tld}$/]

Global Options

• VagrantDNS::Config.listen: an Array of Arrays describing interfaces to bind to. Defaults to [[:udp, "127.0.0.1", 5300]].
• VagrantDNS::Config.auto_run: (re)start and reconfigure the server every time a machine is started. On by default.

Issues

• A records only
• no ipv6 support
• OS X only
• Alpha code