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

Selfhosted

40731 readers
344 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 2 years 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
[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

For local DNS home.arpa is I think what we're 'supposed' to use, but I use .lan

Only use another domain name if you actually have it registered, like myname.net or something. As a bonus you can then get a wildcard letsencrypt SSL cert for easy HTTPS.

[–] [email protected] 1 points 1 year ago (1 children)

Why should you only use ones you own, even if it's just local network?

[–] [email protected] 3 points 1 year ago

Because of interference with existing domains. Say you set a computer on your network to mypc.google.com, that won't work because the DNS server will lookup google.com as an external domain.