this post was submitted on 08 Aug 2024
498 points (99.0% liked)

Selfhosted

40347 readers
464 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
you are viewing a single comment's thread
view the rest of the comments
[–] DarkMetatron@feddit.org 10 points 3 months ago (1 children)

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.

[–] aesthelete@lemmy.world 4 points 3 months ago (2 children)

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.

[–] witten@lemmy.world 3 points 3 months ago (1 children)

You don't even need a star cert.. The DNS challenge works for that use case as well.

[–] aesthelete@lemmy.world 2 points 3 months ago (1 children)

I agree, if you're putting your internal domain names into the public DNS you do not need a star cert.

[–] emptiestplace@lemmy.ml 1 points 3 months ago (1 children)

No, you don't need to do that.

[–] aesthelete@lemmy.world 2 points 3 months ago

Maybe I'm missing something then, how would you pass a DNS challenge?

[–] DarkMetatron@feddit.org 2 points 3 months ago

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.