42
DNS hijacking
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Aug 2023
42 points (97.7% liked)
Selfhosted
39677 readers
408 users here now
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:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
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.
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.
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.