this post was submitted on 28 Jul 2023
18 points (90.9% liked)

Selfhosted

39903 readers
463 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 1 year ago
MODERATORS
 

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
[–] IsoKiero@sopuli.xyz 5 points 1 year ago (1 children)

It's doable for sure. You just need a way to sync the data between locations so that every DNS server responds with the same records, but that's pretty much it. I do that for a (very small) business with ispconfig, but there's plenty of options around starting from building your own. On the question if you should it's a bit more difficult. Running a DNS server out in the wild isn't the most complex thing to do, but it's also a thing where you can break pretty much everything else you're running very easily if you mess something up.

It's a bit difficult to say if you should. From my point of view, if you really know what you're getting into and doing you're not asking if you should around the internet and (in general) if you ask if you should do it then (way more often than not) the answer is 'no'. If you know how to write zone files manually (not that you really need to, it's just a thing you can do when you have enough understanding on DNS and things related), understand how axfr and loads of other tech works, then sure, go for it. But, and I know I'm repeating myself, if you ask if you should (to me) it's a sign that you don't know enough.

[–] muddybulldog@mylemmy.win 2 points 1 year ago

I can see wanting to run your own DNS to serve personal clients for privacy purposes but for self-hosting class stuff I can think of plenty of downsides and zero upsides to privatizing this.

Definitely a “yeah, you could” vs. “yeah, you should” situation.