> An installation of Debian 13, by default, uses DNS servers of your local ISP which are usually very slow.
I hear this a lot, but I wonder how often it's actually true. Ping-wise I get sub-millisecond time to my ISP's resolver, ~8ms to CF and Google, and ~4ms to Quad9. DNS wise (as reported by dig) I get ~20ms for a cache miss with my ISP and Quad9, and ~40ms with CF and Google.
Considering TFA recommends benchmarking repository mirrors to select the fastest one, I'm not sure why the same recommendation isn't made for DNS resolvers.
Milpotel · 1h ago
The not optimising, that's making it insecure and bloated.
AndrewOMartin · 41m ago
Indeed, it would be useful to know why each of these points are not enabled by default (including a huge amount of non-free and less verified software is an obvious one). In particular the `sbin` one I assumed because it's stuff you'd only use as root and they already have it on their path. E.g. `reboot` might say "not found" but `sudo reboot` will work.
I hear this a lot, but I wonder how often it's actually true. Ping-wise I get sub-millisecond time to my ISP's resolver, ~8ms to CF and Google, and ~4ms to Quad9. DNS wise (as reported by dig) I get ~20ms for a cache miss with my ISP and Quad9, and ~40ms with CF and Google.
Considering TFA recommends benchmarking repository mirrors to select the fastest one, I'm not sure why the same recommendation isn't made for DNS resolvers.