Selfhosted

44364 readers

590 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 2 years ago

MODERATORS

[email protected]

How do you host your DNS sinkhole/resolver? (self.selfhosted)

submitted 4 days ago* (last edited 3 days ago) by ohshit604 to c/[email protected]

53 comments fedilink hide all child comments

Currently have nice long docker compose file that hosts my PiHole V6 container (along with a bunch of other containers) however, reason i ask this question is because whenever I go to pull an updated image and recreate the container I experience about 20 minutes of no DNS resolution which to my knowledge is due to the NTP clock being out of sync.

What’s the best way to host a DNS sinkhole/resolver that can mitigate this issue?

Was thinking of utilizing Proxmox & LXC but I suspect I’ll get the same experience.

~~Update: Turns out PiHole doesn’t support two instances, I got both of them on separate devices also set the 2nd DNS server in my routers WAN & LAN DNS settings which did in fact split DNS between both instances however, I lost access to my routers web-ui, my Traefik instance & reverse proxies died and I lost all internet access.~~

~~So, don’t do what I did.~~

Update 2: So everything I said in my first update let’s disregard that, turns out I had my router forcing all DNS to PiHole server 1 which caused my issues mentioned above.

Two servers appears to work!

you are viewing a single comment's thread
view the rest of the comments

[–] ohshit604 1 points 3 days ago* (last edited 3 days ago) (1 children)

I tried running unbound + PiHole however, my experience was less than ideal.

I was able to forward all DNS queries without issues however, PiHole wasn’t receiving response times from unbound which caused some of my other docker containers to bug out with timeout errors.

PiHole makes monitoring the network convenient which is kinda why I don’t wanna lose it, unbound doesn’t appear to have a web-ui natively.

[–] [email protected] 2 points 3 days ago (1 children)

Ive been using it with opnsense and it has a lot of built in logging and reporting. Maybe not as pretty as pihole but it works great

[–] ohshit604 1 points 3 days ago* (last edited 3 days ago) (1 children)

Ive been using it with opnsense and it has a lot of built in logging and reporting.

Never did a lot of research into opnsense, from what I can see it’s a whole OS. I might consider it because I feel Proxmox (which I use currently for my host OS) isn’t getting utilized to its fullest.

Maybe I’ll go network monitoring instead of virtual environment spin-ups 🤔

[–] [email protected] 1 points 3 days ago (1 children)

Why not both

[–] ohshit604 1 points 3 days ago* (last edited 3 days ago)

Huh, while I was typing this comment I decided to read the minimum hardware requirements and turns out I only need to reserve 2 cores for the vm.

While I’m not exactly hosting proxmox on server grade hardware, I think I can spare 2 maybe 3 cores, 4 is a bit of a stretch I think given that 6 are already reserved for my headless Debian 12 vm + Docker engine.