this post was submitted on 11 Oct 2025
74 points (100.0% liked)

Selfhosted

52199 readers
452 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I've been using pi-hole for the last 3 or 4 years and I'm pretty satisfied with it. Now I'm thinking about the next step. Nowadays I have my local network and a tailscale to access my hosts. I'm thinking about a DNS solutions to solve the names on the locla network and thru tailscale simultanely, while been able to block ads on DNS like pi-hole do. What do you think would be a better solution for this next step? I've only used bind before, but I think and old dog can learn a new trick.

you are viewing a single comment's thread
view the rest of the comments
[–] non_burglar@lemmy.world 1 points 10 hours ago* (last edited 10 hours ago) (1 children)

Not sure what you mean by "network based dns".

Hard-coded DNS is in the application, you cannot change this from any dhcp option. Browsers do it, lots of versions of prime video apps do it. Google nest and home devices are famous for this.

You can write a NAT rewrite rule at your router to catch any UDP or TCP request on port 53 and send it to your ad-blocking DNS server/forwarder, but you won't be able to stop DoH (DNS over https), which just leaves the subnet encrypted on 443.

[–] q7mJI7tk1@lemmy.world 1 points 7 hours ago (1 children)

I was being too simplistic in my other reply. I was referring to basic router based DNS and NextDNS as the upstream resolver.

I don't have an answer for hard coded DNS when it comes to NextDNS, which is essentially an upstream resolver with block lists functionality.

And to be honest, I misinterpreted OPs original question which was to take PiHole to the next level, whereas NextDNS is an alternative to.

I can run app based routing and blocking on my router, but whether that would restrict DNS for those services I don't know.

Thanks for the clarification, you've got me wanting to pursue more DNS control now!

[–] non_burglar@lemmy.world 1 points 6 hours ago

I can run app based routing and blocking on my router, but whether that would restrict DNS for those services I don't know.

That's the double-edged sword of DNS over https. It allows us to hide our DNS queries from local ISP and others, but it also allows applications to hide theirs also. It just looks like encrypted web traffic to your router.