4 ms·
Unfortunately, with at least Chrome and Firefox moving to DNS-over-HTTPS, they are the entities deciding on address resolution for 99% of average-user requests.
by byuu 7y ago
Unfortunately, with at least Chrome and Firefox moving to DNS-over-HTTPS, they are the entities deciding on address resolution for 99% of average-user requests.
I would agree with you in principle however, in which case there's an even more impossible goal: get Microsoft, Apple, Google, and every Linux/BSD distro to agree to a new OS-level alternate domain name resolver that functions out of the box. And also stop Google and Mozilla from rolling out browser-level DoH.
- justinclift 7y agoWonder if this means Cloudflare - and/or the other termination points for DNS-over-HTTPS - could be an interesting place to start adding an alternative DNS resolution system? Then it wouldn't need to be done by any browsers... if the DNS-over-HTTPS end point provider does the additional name resolution, it should "just work".
- syshum 7y agoYes because that is what the internet needs, to have CloudFlare in control over more and more of it
- mygo 7y agoWe’re here because a private company has taken over .ORG I see what you’re saying in theory, but it can’t be cloudflare or a private company or else it’s more of the same.
- justinclift 7y agoIf it's done as a coalition of the places which provide DNS-over-HTTPS, it might work. :)
- mygo 7y agoNegative. Private equity has billions to pay with. Everyone has a price.
- int_19h 7y agoThe OSes appear to be signing up for DoH as well.