this post was submitted on 10 Jul 2023
5 points (100.0% liked)

Selfhosted

46677 readers
1351 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?

top 31 comments
sorted by: hot top controversial new old
[–] VerifiablyMrWonka@kbin.social 4 points 2 years ago (1 children)

I just bought an actual domain and use that πŸ˜…

As an added bonus, letsencrypt works with no effort.

[–] karlthemailman@sh.itjust.works 0 points 2 years ago (1 children)

Same here. Well worth it for $10 a year

[–] faultyaddress@lemmy.fmhy.ml 0 points 2 years ago (1 children)

I bought domain from joker.com, 10 years for $33

[–] priit123@lemmy.world 1 points 2 years ago (1 children)

What? How they sell for so long?

[–] faultyaddress@lemmy.fmhy.ml 1 points 2 years ago* (last edited 2 years ago)

I don't know but they do. I picked the cheapest name I could find and went with it.

Checked and they still do sell domains for 10y but price has gone up.

[–] aezart@lemmy.world 3 points 2 years ago

I use a subdomain of a domain name I own.

[–] redcalcium@c.calciumlabs.com 2 points 2 years ago* (last edited 2 years ago) (3 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 2 points 2 years ago (2 children)

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

[–] zorflieg@lemmy.world 3 points 2 years ago

A long time ago Microsoft and some teaching sources used .local in example documentation for local domains and it stuck. Like contoso.com was Microsoft's example company. I was taught to use .local decades ago and it took a very long time to unlearn it.

[–] sifrmoja@mastodon.social 1 points 2 years ago

@dpflug @redcalcium @zephyr it is reserved for mDNS.

[–] erre@feddit.win 1 points 2 years ago (1 children)
[–] redcalcium@c.calciumlabs.com 1 points 2 years ago* (last edited 2 years ago)

Interesting, so this is the latest recommendation? Which is probably why I haven't seen it in the wild yet, at least in my circles.

Which means they probably going to ~~cash out~~ release gTLDs for .intranet, .internal, .private, .corp, .home and .lan soon...

[–] vegetaaaaaaa@lemmy.world 1 points 2 years ago* (last edited 2 years ago) (2 children)

A problem with the .lan TLD (maybe others from this list) is that web browsers do not consider it a TLD when you type it in the address bar, and only show you the option to search for that term in your default search engine. You have to explicitly type https:// before it, to have the option to visit the URL.

E.g type example.com in the address bar -> pressing Enter triggers going to https://example.com. Type example.lan -> pressing Enter triggers a search for example.lan using your default search engine.

[–] distantorigin@kbin.cafe 5 points 2 years ago

Little known trick--or perhaps everyone knows it and is quietly laughing behind my back--with Chromium browsers and Firefox (and maybe Safari, I'm not sure), you can add a slash to the end of an address and it will bypass the search.

So, for example, my router on the LAN goes by the hostname "pfsense". I can then type pfsense.lan/ into my address bar and it will bring me to the web UI, no HTTP/s needed.

You can throw a / after to force it to recognize as a URL too.

[–] Makussu@feddit.de 2 points 2 years ago

There actually is a correct awnser: home.arpa
See https://www.ctrl.blog/entry/homenet-domain-name.html

[–] aezart@lemmy.world 1 points 2 years ago

I use a subdomain of a domain name I own.

[–] Merc_@lemm.ee 1 points 2 years ago* (last edited 2 years ago)

I use home.arpa for all my LAN hosts.

[–] knaak@lemmy.world 1 points 2 years ago

.home.lan for me.

[–] ThorrJo@lemmy.sdf.org 1 points 2 years ago

I use .lan for everything the router can resolve names for, and .local for Avahi mDNS 😈

[–] nsaobserverbot@kbin.social 1 points 2 years ago

fritz.box for the machines themselves because Fritz!BOX (although handed out by Pi-Hole),but .lan for anything going over the local proxy towards the same machine for TLS.

Some machines use my custom domain name instead of .lan, if they need to be accessible from outside. So these last ones go directly over the local proxy internally, but automatically over CloudFlare Tunnel and Authentik when not at home. The proxy being Caddy.

[–] Ori@sacredori.net 1 points 2 years ago

I tend to use .local

[–] taladar@sh.itjust.works 1 points 2 years ago (1 children)

You shouldn't use .local for your manually defined local domain names if you plan to ever use mdns/avahi/bonjour/zeroconf.

[–] Mr_Figtree@kbin.social 0 points 2 years ago (1 children)

And .box has been registered as a generic TLD now, so you could run into external .box domains.

[–] Perhyte@lemmy.world 1 points 2 years ago

Hopefully AVM gets to register fritz.box then, because they've been setting up their customers with that as their internal domain for ages...

[–] MangoPenguin@lemmy.blahaj.zone 1 points 2 years ago* (last edited 2 years 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.

[–] beeng@lemmy.fmhy.ml 1 points 2 years ago (1 children)

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

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.

[–] preciouspupp@sopuli.xyz 0 points 2 years ago (1 children)

There’s a draft rfc that defines β€œ.home.arpa” as an internal. It looks stupid and totally misses the point, but works.

[–] erre@feddit.win 0 points 2 years ago (1 children)
[–] preciouspupp@sopuli.xyz 1 points 2 years ago

Yeah, but it’s a proposal, so not really better that .lan.