search

BerlinVagrant / vagrant-dns

A plugin to manage DNS records for vagrant environments
MIT License
490 stars 50 forks source link

List dns entries in RubyDNS #56

Closed bertramn closed 6 years ago

bertramn commented 6 years ago

After landrush is dead and buried, I am looking for a new dns solution.

Is it possible for this plugin to somehow list the DNS entries in the RubDNS? Also where are these records stored, are they just held in memory or written to disk to survive restarts? Last but not least, I noticed that the DNS server is restarted every time I do a vagrant reload, if I run a vagrant file with multiple machines will any old configuration be flushed?

fnordfish commented 6 years ago

Hi @bertramn

general design goals are described in (the quite old) PLATFORM_SUPPORT.md.

Is it possible for this plugin to somehow list the DNS entries in the RubDNS?

There is no build-in command for doing so. But: see next point (Issue/PR welcome :))

Also where are these records stored, are they just held in memory or written to disk to survive restarts?

Configured dns patterns are stored in ~/.vagrant.d/tmp/dns/config. It's basically a big list of regex-patterns mapping IPs (like this: "^(.*.)?foobar.test$": 33.33.0.11) This file gets updated (new records added) during the start of a box. That's why the dns server gets restarted. This file is not cleared up automatically.

... if I run a vagrant file with multiple machines will any old configuration be flushed?

No. (see above)

bertramn commented 6 years ago

thanks @fnordfish, took the plugin through the paces and looks like its up to the job of replacing landrush. Having a command like vagrant dns --list to list out the patterns of the config file would be a nice enhancement. The other thing that could be improved is when a VM is destroyed, any pattern it registered could be cleaned up in the config file and the dns service reloaded. This way we'd never have to hack the config file directly. Great job :)

fnordfish commented 6 years ago

Right. Would you mind creating two separate issues?

Regarding the cleanup: removing configured patterns should be doable, but not detecting changes (editing the Vagrantfile). I think, that’s why most ppl just trash the entire config and let it auto-generate with the next start

fnordfish commented 6 years ago

released as v2.1.0