On Thu, May 23, 2024 at 2:54 PM <to...@tuxteam.de> wrote: > > On Thu, May 23, 2024 at 01:50:21PM -0400, Jeffrey Walton wrote: > > On Thu, May 23, 2024 at 12:08 PM Paul M Foster <pa...@quillandmouse.com> > > wrote: > > > > > > On Thu, May 23, 2024 at 12:54:31AM -0400, Jeffrey Walton wrote: > > >[...] > > > > Also, I think you should be using *.home.arpa, and not *.lan. > > > > home.arpa is reserved for private use by ICANN and the IETF. I suspect > > > > *.lan is not reserved for private use. > > > > > > On a LAN, you can use anything you like. I've used .mars.lan for decades > > > with no difficulty. > > > > Citation, please. > > No need. It just works. Of course, if you have domain names > in your LAN which also is "out there", you won't "see" both.
Perhaps that's why you _can't_ use anything you like; and that's why you should use domains reserved for private use. Related reading is Brand TLDs (a/k/a/ Vanity Domains) at <https://icannwiki.org/Brand_TLD>. > If your LAN is isolated, you can basically do whatever you > want. And then act surprised when networking breaks :) > And then there are "special" TLDs (.local, I'm looking at > you) where you'll get lots of fun effects should you decide > to use them (zeroconf, I'm looking at you :-) I _think_ .local is reserved for mDNS. See <https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml>. It looks like .internal and possibly .private are coming soon. See <https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024> and <https://www.theregister.com/2024/01/29/icann_internal_tld/>. Jeff
