Selfhosted
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!
view the rest of the comments
I get that - but part of the reason for the current situation is that DNS is such a bad protocol that is risky to leave in unskilled hands. You can do damage beyond just your host. DNS is a big target and servers can find themselves participating in DDOS attacks. The big players do traffic analysis and rate limiting to minimize these things.
It's not that it's "hard to run a name server" it's that it's tricky to configure one correctly so as to be a "good neighbor" on the internet. Most homegamers only need a single "A" record anyway - maybe some CNAMEs. It's not like you need anything complicated. And if you don't have a static IP address then you definitely want your DNS server to be updatable easily with a new IP. Updating NS records is more complicated.
Running an internal name server is fine and a great experience. You can do so much more on your own network than you would likely do with a public name server anyway.
Only doing resolution for your own domain and dnssec solve pretty much all those issues and is pretty darn easy.
And I did say that the web gui is what you need to lock down, DNS has no vulnerabilities exploitable through port 53 that lets an attacker take control of the server.
You're saying "If you configure your DNS server properly and understand how it works then it can be setup securely."
I'm saying "Have you seen the questions in this community???"
... Touché