Open patcon opened 12 years ago
Not sure if that's what you mean, but for me vagrant dns --list
shows a list of some old domains I must have used for tests many moons ago.
So, how/where does this plugin cache such settings?
This are two different things. First of all, the original issue was from 2012 (sorry for letting it collecting dust) and vagrant dns --list
didn't exist back than, but it also seems to refer to browsers (or probably any client doing DNS requests) caching DNS entries. And yes, that's issue where we might do something about it, but it's not vagrant-dns caching anything, it's either the client (browser) and/or some part of your operating system (eg: https://duckduckgo.com/?q=mac+flush+dns)
Vagrant-dns starts a DNS server which reads from a configuration file (usually) ~/.vagrant.d/tmp/dns/config
and vagrant dns --list
basically dumps an interpreted version of that file.
Seems that the rules sometimes stick around, even we explicitly refresh our browser. Not particularly harmful at the moment, but might make people anxious as their system is getting into a state that they're unsure how to revert.