4 ms·
It's a complicated topic with lots of pros and cons, which also depend on the role you have. Masking network configuration problems is great for a user, not as
by ketzu 6y ago
It's a complicated topic with lots of pros and cons, which also depend on the role you have. Masking network configuration problems is great for a user, not as great for the admin, but I believe this should be something the network admins test for, not every user ever in the network.
The exposure of the IP address is another aspect. While DNS can expose more info, the complaint also includes IP addresses specifically. I believe this has severe implications: Does any outside communication need to be acked on setup? Should ntp servers be preconfigured on OSes at all? I wonder which other services depend on similar behaviour. Will it end up like consent forms on websites?
I personally think a fallback DNS which masks network errors is a nice thing, as systems should be resilient for users. Errors just need to be discoverable for admins. I usually want things to work, not debug errors of others (or even my own).
- Daho0n 6y agoIf you want a fallback you (IE. Systemd) should fall back on a recursive resolver you provide. Not a random external service.