this post was submitted on 08 Aug 2024
497 points (99.2% liked)

Selfhosted

39250 readers
278 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
[–] [email protected] 34 points 1 month ago (18 children)

Why do I care what ICANN says I can do on my own network? It's my network, I do what I want.

[–] [email protected] 35 points 1 month ago (12 children)

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/

[–] [email protected] 1 points 1 month ago (10 children)

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

[–] [email protected] 2 points 1 month ago

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

load more comments (9 replies)
load more comments (10 replies)
load more comments (15 replies)