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

Selfhosted

61674 readers
101 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 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
[–] hamsda@feddit.org 6 points 10 months ago* (last edited 10 months ago) (1 children)

I don't know about tailscale, but it seems pihole has got you covered with local DNS, if you're willing to set the local DNS records manually.

I use pihole as selfhosted DNS server for all my servers and clients. I don't have many local DNS records (only 2), so if you handle a great amount of ever-changing DNS records, this might not be for you.