Selfhosted

40731 readers

366 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

run my own authoritative DNS (lemmy.world)

submitted 1 year ago by johnnychicago@lemmy.world to c/selfhosted@lemmy.world

12 comments fedilink hide all child comments

Hello --

I have my DNS with a cloud provider that I want to stop using, and was considering where to move it (a few domains with a handful entries each). At some point I was wondering if I should run it myself. I have two VPS' in different data centers with fixed IP addresses, and I read up a bit - seems like this is doable. I am not set on what software to use. I would like it to run in a container. Does anybody have any recommendations, positive or negative?

Thanks :)

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

[–] wiki 5 points 1 year ago

I think it's pretty doable, but there are some things you should think about:

Email delivery dependencies: If you use email addresses on the domains you're hosting, problems in DNS will cause you to not be able to receive emails. This can be a problem if you plan on monitoring your DNS with alerts via email, or if you need to do password recovery via email to access your VPS accounts, for example. Check if this applies to other services you might be running.
You'll need to understand glue records to setup at least one of your domains.

For my domains, I'm running nsd in two different VPSes, and the way that I edit my zones is that I have a script that converts a shorthand format (that I came up with) to a standard zone file and then rsyncs (using hostnames declared in my .ssh/config files) the zone files and nsd configuration files to both servers. The script then reloads nsd.

I chose nsd because it felt like the simpler option, no troubles so far. I use them directly on my debian hosts, no containers.

I have no monitoring, but I should. My terrible excuse is that the infrastructure I'm running is not critical and it's on the same hosts as my nameservers, so they usually go down together. I wouldn't put client domain names in there without monitoring.