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
Try using .com for your internal network and watch the problems arise. Their choice to reserve .internal helps people avoid fqdn collisions.
See also https://traintocode.com/stop-using-test-dot-com/
Well as long as the TLD isn't used by anyone it should work internally regardless of what ICANN says, especially if I add it to etc/hosts
Sure, you can do whatever you want. You could even use non-rfc1918 addresses and nobody can stop you. It's just not always a great idea for your own network's functionality and security. You can use an unregistered TLD if you want, but it's worth knowing that when people and companies did that in the past, and the TLD was later registered, things didn't turn out well for them. You wouldn't expect .foo to be a TLD, right? And it wasn't, until it was.
Ah good point. I guess a future-proofed guarantee that the domain will never be used externally would be easier to use than trying to somehow configure my DNS to never update specific addresses.
German router and network products company AVM learned the hard way that this is a bad idea. They use fritz.box for their router interface page and it was great until tld .box became publicly available and somebody registered fritz.box.
Having a reserved local/internal only tld is really great to prevent such issues.
I agree that this is a good idea, but I wanted to add that if someone owns a domain already, they can also use that internally without issue.
If you own a domain and use Let's Encrypt for a star cert, you can have nice, well secured internal applications on your network with trusted certificates.
You don't even need a star cert.. The DNS challenge works for that use case as well.
I agree, if you're putting your internal domain names into the public DNS you do not need a star cert.
No, you don't need to do that.
Maybe I'm missing something then, how would you pass a DNS challenge?
That is great when using only RFC 1918 IPv4 addresses in the network, but as soon as IPv6 is added to the mix all those internal only network resources can becomes easy publicly available and announced. Yes, this can be prevented with firewalling but it should be considered.
If you just run a personal private network, then yea pick anything because you can change it fairly easily. Companies should try to stick to things that they know won’t change under them just to avoid issues