Change the DNS servers on you devices to a DoT or DoH provider.
The ISP can't intercept and rewrite your requests if they are in a secure session.
On modern versions of Windows (and probably other OSes), you can configure it to use DNS over HTTPS with a service like Quad9 or Cloudflare, which will fix this.
To do this across all your devices, even those that don't support DoH, install AdGuard Home on a home server or Raspberry Pi or your PC if it's always on. ISPs can't intercept DoH requests. Then configure your router to set the DNS server to your AdGuard Home server.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| HTTPS | HTTP over SSL |
| IP | Internet Protocol |
| PiHole | Network-wide ad-blocker (DNS sinkhole) |
| SSL | Secure Sockets Layer, for transparent encryption |
| TLS | Transport Layer Security, supersedes SSL |
| VPN | Virtual Private Network |
[Thread #56 for this sub, first seen 16th Aug 2023, 18:25] [FAQ] [Full list] [Contact] [Source code]
You missed two that I’d like to know about. DoH and DoT. Thanks, robot!
DNS over HTTPS, DNS over TLS
Thank you, I had to figure it out myself haha.
Good bot.
So is your ISP blocking or redirecting outgoing requests on port 53? You said you can't set dns servers on your own devices so I'm just trying to understand why that doesn't work.
So is your ISP blocking or redirecting outgoing requests on port 53?
Correct.
Wow. What kind of bullshit ISP blocks outbound DNS requests? I would bitch loudly at them as they have no valid excuse for doing that. Anyway... In that case you have a few options. You can use DNS over https but that's supported primarily by browsers. Not so much other desktop applications. I would get a router that's capable of WireGuard and connect it to ProtonVPN (or another VPN service of your choice). You don't have to route all traffic over VPN if you don't want to but at least you'll be able to use whatever DNS server you want.
In Italy Vodafone blocks that request for "safety" and they were forcing users to use a custom proprietary shitty router where you could barely change the wifi password
US ISPs. It's amazing what you can get away with when you own enough politicians
The bypass is to run your own router, distribute locally hosted dns servers (either the router or pihole) and the dns servers get their lookups over dns over https (443) and your provider can't intercept that since it looks like regular encrypted Web traffic just like they shouldn't be able to inspect your netbank.
Australia is different but these isps who do that generally have a +$5 per month plan to go to a static public rout able public Up (instead of cgnat) and unfiltered Internet. They usually are more allowing mum and dad to filter the Web so their kids can't get too far off track. Maybe just double check on your ISP portal settings but I'm going to assume you're not in aus.
I'm in MX. It's not like they actually care about giving the consumer proper permissions. The "business" solution keeps the DNS shenanigans.
Setup a local DNS server in your local network, and configure it to forward everything to an external DNS provider over TLS (port 853 usually). This is known as DNS over TLS (or DoT as other people mentioned).
I personally like https://cyberia.is
If you have the option to use a DNS on a different port, you can take a look at OpenNIC. There are a number of servers available that answer on multiple ports. Development has been stalled for a few years now but we're still keeping the back-end stuff running. You can find info at https://www.opennic.org/ and https://servers.opennic.org/
Set up your router to use DNS-over-HTTPS if it supports it.
If not you can install Adguard Home somewhere, set your devices to use that for DNS, and set it to use DNS-over-HTTPS for the upstream servers.
Just throwing out a couple of other solutions I didn't see mentioned for DoH/DoT:
Both of those support encryption and allow for DNSBL. If you are wanting to hand out DNS entries over DHCP it may a problem with your ISPs router there. Either replace it, sit one you do control between it and your network, or run DHCP snooping from a switch to restrict it's DHCP.
This Blocky?
Will keep them in mind, thanks a lot.
Yep, that's the one. You just set your upstream default to something like tcp-tls:1.1.1.1:853 for DoT (which is what I use anyway).
Good documentation on other features like adblocking,caching,etc: https://0xerr0r.github.io/blocky/v0.21/configuration/
Why can you not set your own DNS on your devices?
If you mean you can’t set your DNS automatically that would be due to DHCP. You can setup your own DHCP server and set the DNS IP to whatever you want (8.8.8.8 etc).
PiHole should handle all this for you all while blocking ads and being a local DNS resolver.
Why can you not set your own DNS on your devices?
I can, they get redirected to my ISPs DNS, no matter what. This was not an issue with my pervious company.
How are you detecting this? Just curiosity
Often, if you try to go to a non-existent domain, it'll still return an IP address that loads a "this site doesn't exist" page hosted by the ISP, often full of sponsored links, similar to a domain parking page.
It's trivial to do this. DNS requests are unencrypted and can easily be modified by an ISP, even if you use a custom DNS server like Google's 8.8.8.8 or Cloudflare's 1.1.1.1. You need DNS over HTTPS or a similar technology to prevent this happening.
hijacking dns is also my provider's first action when you're late paying the bill. by ip or doh or a long-lived dns cache and you're still going, but anything looked-up via a 'regular' dns server goes nowhere. that gets you another 2-3 weeks until they deny the modem from even authenticating.
Look into Pi-hole. It's an easy-to-setup DNS server which can run on a Raspberry Pi (or a Linux desktop/server if you have one.) You can then set your devices' DNS servers to the local address where the Pi-hole is running. Since it would be running on your local network, any requests to it shouldn't go through your ISP in the first place. I'd still recommend getting your own router anyways because this kind of ISP fuckery is more common than you'd expect. Plus, your exact configurations follow you anywhere you move. If you do end up getting one, set the local DNS server in the DHCP settings of your router to avoid having to set it on each device.
Doesn't the RPi still go through the ISP? You'd still have to find a way to bypass their hijacking attempts, just on a different device this time.
Dot or doh will stop the DNS rewrites.
You'd have to use DNS over HTTPS, DNS over TLS, or DNS over QUIC. As far as I know, PiHole doesn't support these out-of-the-box, so AdGuard Home is a better choice (it's like PiHole but more powerful).
I know PiHole had plans to implement this though, so maybe they do support it now.
You can do it. I set mine up ages ago. https://docs.pi-hole.net/guides/dns/cloudflared/
It's not out-of-the-box though, and requires a bunch of manual setup. On AdGuard Home you just need to enter the DNS URL into the UI and that's it.
Using your own router is the best way, I just finished setting up DoH, I am using a router with OpenWRT, so installed https-dns-proxy with luci-app-https-dns-proxy. It has options to hijack DNS so that all local devices will be routed to the router DNS even if they try to use a DNS server directly.
More information can be found here.
Adguard home is a better choice as it supports DoT and DoH, which OP will need to use to be able to bypass their ISPs DNS hijacking.
Pihole only supports unencrypted DNS on port 53 which is what the ISP is targeting.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!