this post was submitted on 10 Jul 2023
40 points (97.6% liked)

Selfhosted

40083 readers
593 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
 

There are many DNS names options. Which one do you use?

you are viewing a single comment's thread
view the rest of the comments
[–] redcalcium@c.calciumlabs.com 19 points 1 year ago* (last edited 1 year ago) (10 children)

According to IETF, you should only use .intranet, .internal, .private, .corp, .home or .lan for your private network ( RFC 6762 Appendix G ). Using other TLDs might cause issues in the future, especially since new gTLDs seems to show up every few months or so, which can collide with the TLD you use for your local network.

[–] dpflug@hachyderm.io 4 points 1 year ago (3 children)

@redcalcium
Really? Not .local? Why is it the default on so much?
@zephyr

[–] sifrmoja@mastodon.social 4 points 1 year ago (1 children)
[–] dpflug@hachyderm.io 1 points 1 year ago

@sifrmoja
Ah, yep. Now that you say it. Thanks for cluing me in.
@redcalcium @zephyr

load more comments (1 replies)
load more comments (7 replies)