4 ms·
> There's a strain of Unix sysadmin criticism against DoH that says it's wrong for browsers to co-opt DNS resolution at all, and that they should use the system
by Faark 7y ago
> There's a strain of Unix sysadmin criticism against DoH that says it's wrong for browsers to co-opt DNS resolution at all, and that they should use the system's resolver.
It's perfectly reasonable. I don't want each app maintaining its own config and having to gain in-depth understand of its custom solution when using another network. Just had that fun with gradle proxy settings in a global configuration file making downloads appear forever with no visible error message. Could have spend that quite a bit of time a lot more productive / enjoyable.
These kind of standards exist for a reason. The problem is Mozilla not having a way to distinguish an unaware user using the good old way from someone specifically preferring it. OS vendors could help, but relying on them doesn't seem like a good plan either.
- tptacek 7y agoIt is not perfectly reasonable. Different applications have different requirements, and the applications running on my OS should not all be confined to the lowest common denominator of what the developer who broke the build and is stuck maintaining the DNS code decides to implement. When the operating system provides performant DoH lookups for all applications, then sure, lobby your browser to use that code instead of their own.
- pvg 7y agoof what the developer who broke the build This is vicious slander. Would the developer who merely broke the build get to write an entirely new system resolver implementation in C++ from scratch, get it into a major OS release and thus break stuff for zillions of users until the whole thing has to be rolled back, never to be seen again? I think not. https://www.macrumors.com/2015/05/26/apple-discoveryd-replaced-with-mdnsresponder/ https://www.macrumors.com/2015/05/26/apple-discoveryd-replac...