4 ms·

> There is no actual technical reason There exist pure technical reasons too, from address translation to DNS-level routing and load balancing. For example for

> There is no actual technical reason There exist pure technical reasons too, from address translation to DNS-level routing and load balancing. For example for ipv6-only network to access ipv4 resources there needs to be something like NAT64 embedding ipv4 addresses into ipv6 ones, but that would require overwriting DNS responses with DNS64 to actually work [1] [1] https://en.wikipedia.org/wiki/IPv6_transition_mechanism#DNS64 https://en.wikipedia.org/wiki/IPv6_transition_mechanism#DNS6... Keep in mind, encryption is not privacy. Encrypting DNS queries to a 3rd party resolver doesn't improve your privacy, it's a fight for control, not privacy. ISPs will still violate your privacy to the same extent, except said 3rd party will be able to do that too. If your ISP is not trustworthy the only way to save yourself from it is to use something like a VPN which effectively gives you a different ISP of your choice.

knorker 7y ago
> DNS-level routing and load balancing How do you mean? Why should my ISPs hijack communication between me and a content provider and reroute it? This is as if I'm in a phone meeting and when I say "let me call you back at 15:00" the phone company injects "19:00" instead, because that's a time the phone network is less loaded so it'd help them. > NAT64 embedding ipv4 addresses into ipv6 ones NAT64 is a good point, actually. But at least in 2019 if you're on IPv6 and switch to your own DNS server that doesn't do DNS64, then it just plain won't work. I doubt Firefox or Chrome will have implementations that break like that. > If your ISP is not trustworthy Or country.
- zzzcpan 7y ago
  Some authoritative DNS servers may respond with incorrect IP addresses for specific IP subnets of an ISP (i.e. pointing to unreachable or slow far away servers), so it could be useful to fix this either statically or by forwarding domains to another DNS resolver which gets proper responses. Things like that.
  - knorker 7y ago
    My experience is that things like that will obviously break more than it fixes. One cannot assume to know better between two third parties like that. Half of global loadbalancing is getting around ISPs doing stupid shit they shouldn't have been messing with.

knorker 7y ago

> DNS-level routing and load balancing How do you mean? Why should my ISPs hijack communication between me and a content provider and reroute it? This is as if I'm in a phone meeting and when I say "let me call you back at 15:00" the phone company injects "19:00" instead, because that's a time the phone network is less loaded so it'd help them. > NAT64 embedding ipv4 addresses into ipv6 ones NAT64 is a good point, actually. But at least in 2019 if you're on IPv6 and switch to your own DNS server that doesn't do DNS64, then it just plain won't work. I doubt Firefox or Chrome will have implementations that break like that. > If your ISP is not trustworthy Or country.

zzzcpan 7y ago
Some authoritative DNS servers may respond with incorrect IP addresses for specific IP subnets of an ISP (i.e. pointing to unreachable or slow far away servers), so it could be useful to fix this either statically or by forwarding domains to another DNS resolver which gets proper responses. Things like that.
- knorker 7y ago
  My experience is that things like that will obviously break more than it fixes. One cannot assume to know better between two third parties like that. Half of global loadbalancing is getting around ISPs doing stupid shit they shouldn't have been messing with.