4 ms·
That’s why I always resist the desire to lookup (touch/ping/visit) names when changing ips or reissuing certificates by “get on any linux copy to your windows”
by wruza 5y ago
That’s why I always resist the desire to lookup (touch/ping/visit) names when changing ips or reissuing certificates by “get on any linux copy to your windows” method. Once it is cached, you’re doomed to go make some coffee. Only test-visit at the end — and your subnet instantly “updates” on it without delays.
Also googled this out of curiosity: https://www.a2hosting.com/kb/getting-started-guide/internet-and-networking/clearing-the-dns-cache-on-your-computer https://www.a2hosting.com/kb/getting-started-guide/internet-... (How to clear the DNS cache on your computer: win, osx, linux)
- 10000truths 5y agoAlternatively, you can use dig, which bypasses OS-level DNS caching/resolution, and explicitly use a resolver that will respect short TTLs: dig @8.8.8.8 +short aaaa mydomain.com
- laumars 5y agoThere’s nothing wrong with your workflow but personally I prefer checking because beforehand so I have that additional assurance that I’ve made the right change. Baring in mind that it’s easy to flush the DNS cache on most operating systems and dig makes checking resolvers simple.