3 ms·
It's because updating dns does not work reliably so it's always a lot if trail and error which you can only see after the cache updates
by jurschreuder 9mo ago
It's because updating dns does not work reliably so it's always a lot if trail and error which you can only see after the cache updates
- joelthelion 9mo agoCould you make your changes with a low TTL and switch to a longer one once you are satisfied with the results?
- throw20251220 9mo agoHow does that help you if you have to wait for long ttl to expire before the short one takes over?
- nubinetwork 9mo agoYou don't if you flush your cache... on linux, that usually means a reboot unless you run bind or dnsmasq and can just restart them.