There are many DNS names options. Which one do you use?
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.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 typehttps://
before it, to have the option to visit the URL.E.g type
example.com
in the address bar -> pressing Enter triggers going tohttps://example.com
. Typeexample.lan
-> pressing Enter triggers a search forexample.lan
using your default search engine.@redcalcium
Really? Not .local? Why is it the default on so much?
@zephyrA 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.
I just bought an actual domain and use that 😅
As an added bonus, letsencrypt works with no effort.
Same here. Well worth it for $10 a year
I bought domain from joker.com, 10 years for $33
What? How they sell for so long?
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.
*.internal.domain.name
since ssl certs are easier to get when you’re using an owned domain name.