Selfhosted

50456 readers

342 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

DNS server (lemmy.world)

submitted 3 days ago by iturnedintoanewt@lemmy.world to c/selfhosted@lemmy.world

32 comments fedilink hide all child comments

Hi guys! So...I have a self-hosted DNS server. Initially I'd use pihole, with unbound, and the more or less basic blocklists. But from time to time things would start acting wonky. Sometimes a reboot would fix it. Sometimes...not really and I was really not sure what was going wrong, but it was clearly DNS. Changing the clients settings from my own server to something like 9.9.9.9 would immediately get it sorted out.

So I went with an adguard server. In the last few days I've started to notice weird behaviors. Today I've lost the Azure desktop I was connected, and it was very clearly looking like DNS. So I checked...and yup, 9.9.9.9 again would sort it all out. So...I'm not sure what's going wrong. I'm selfhosting these on an LXC container in proxmox. Nothing else seems to have issues connecting, and I see almost no resources being used. Any ideas? Any other DNS server I might be able to try?

Thanks!

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

[–] BlackEco@lemmy.blackeco.com 11 points 3 days ago (1 children)

In my experience with unbound, it tends to return expired records in the hope that they are still valid, causing issues with services hosted in the cloud, where IP addresses rotate regularly. What I did was update the serve-expired-ttl setting in unbound's configuration to 3 hours (down from the default 24h)

[–] iturnedintoanewt@lemmy.world 4 points 3 days ago

Thanks. I think I might rebuild the pihole-unbound server and try again with this setting.