They could technically just drop and traffic over port 53 that is not destined to their own DNS servers. But that’s china level shit. I’ve never seen an ISP control this in North America.
They can also redirect that traffic to their own DNS servers, so you think you are using 3rd party DNS, when you are actually still using theirs. This became legal when the Trump administration got rid of net neutrality legislation.
No, a lot will default to that, but they can’t force you to use any particular dns server. I mean they can, buts a fcc violation at that point I believe
…no, it didn’t. ISPs can’t just block access to specific dns servers Willy nilly. They can slow down specific dns servers of their choice but there’s literally no incentive to do so. Your individual dns traffic isn’t that important I promise.
They do worse than block it, the redirect it to their own servers.
And the data is worth it at volume. They have hundreds of thousands of users, along with the region they are in, as well as data on what websites they visit.
Advertisers have and continue to pay for that data.
I always thought they exist because privacy. Regular old DNS requests are not encrypted so even if you send a request to 9.9.9.9 your ISP can still see it.
At a minimum this meme maker has no idea how TLS, browsers, cookies, or DNS work.
Um, if you use their DNS they do. Some ISPs force that in fact.
How can the ISP force their dns? They can’t know where you got the destination ip from.
They could technically just drop and traffic over port 53 that is not destined to their own DNS servers. But that’s china level shit. I’ve never seen an ISP control this in North America.
They can also redirect that traffic to their own DNS servers, so you think you are using 3rd party DNS, when you are actually still using theirs. This became legal when the Trump administration got rid of net neutrality legislation.
OpenDNS has an article on how to test if your ISP is doing it. https://support.opendns.com/hc/en-us/articles/227988727-How-can-I-tell-if-my-ISP-Allows-Third-Party-DNS-Providers
That is where DNS over TLS and DNS over HTTPS come in. 🙂
Yes of course.
No, a lot will default to that, but they can’t force you to use any particular dns server. I mean they can, buts a fcc violation at that point I believe
It became legal when the Trump administration got rid of net neutrality legislation.
This is why it is so important to get it back, but the current administration is dragging their feet.
…no, it didn’t. ISPs can’t just block access to specific dns servers Willy nilly. They can slow down specific dns servers of their choice but there’s literally no incentive to do so. Your individual dns traffic isn’t that important I promise.
They do worse than block it, the redirect it to their own servers.
And the data is worth it at volume. They have hundreds of thousands of users, along with the region they are in, as well as data on what websites they visit.
Advertisers have and continue to pay for that data.
They don’t have any reason to redirect it. They can see your dns queries either way,
Never had an ISP firewall my DNS. Not sure what country you live in, but it sounds like China at that rate.
It’s usually ISP specific.
Some ISPs in the USA and Germany have been doing it. This is why DNS over HTTPs exists to bypass those blocks.
I always thought they exist because privacy. Regular old DNS requests are not encrypted so even if you send a request to 9.9.9.9 your ISP can still see it.
TLS doesn’t encrypt the host name of the urls you are visiting and DNS traffic is insanely easy to sniff even if you aren’t using your ISPs service.
Yeah, my point exactly.