News for hackers. Stuff that matters.
Re:New gTLD Application for .lan by esskay on Thursday October 08, 2026 @12:21PM (#50007780)
and most people dont use it because its an incredibly poor name.
Re:New gTLD Application for .lan by lokoj on Thursday October 08, 2026 @03:40PM (#50010968)
Why don't they just put home.arpa or .arpa in their search path?
Re:New gTLD Application for .lan by penskymaterial on Thursday October 08, 2026 @05:51PM (#50012884)
What, exactly, makes it poor? Be specific.
Re:New gTLD Application for .lan by simondotau on Thursday October 08, 2026 @06:33PM (#50013374)
I will be very specific about why it is poor. The specific reason is my home network is not the Advanced Research Projects Agency.
Re:New gTLD Application for .lan by brookst on Thursday October 08, 2026 @06:22PM (#50013238)
having two levels, for one. "arpa" not being remotely memorably to non-technical people, for another.
Re:New gTLD Application for .lan by GuB-42 on Thursday October 08, 2026 @06:28PM (#50013309)
- WTF is arpa? (in reality, I know, but there are better names than an obscure reference to internet prehistory)

- it is a second-level domain, why?

- 9 characters (home.arpa) is a lot

I kind of understand the motivation, it is a "technical" domain since it doesn't represent something in the global DNS registry, so it gets the .arpa TLD. However, that's reasoning that it out of touch from normal users. Normal users don't want to be exposed to the technicalities of DNS when they enter something in the address bar, and "myserver.lan" is more meaningful than "myserver.home.arpa", and giving meaningful names is the whole point of DNS.

Re:New gTLD Application for .lan by joquarky on Thursday October 08, 2026 @10:21PM (#50015200)
It feels like a choice that was made at the end of a very long meeting about much more important topics.
Re:New gTLD Application for .lan by denkmoon on Thursday October 08, 2026 @06:47PM (#50013513)
The character count. lan is 3 char, home.arpa is 9. Subjectively, tt is also aesthetically unappealing.

I can't fucking _wait_ to type bender.home.arpa instead of bender.lan. Hyped.

Re:New gTLD Application for .lan by _bernd on Thursday October 08, 2026 @07:30PM (#50013914)
Then use search domain and let your DHCP and DHCP6 server hand that out to clients.
Re:New gTLD Application for .lan by denkmoon on Thursday October 08, 2026 @07:33PM (#50013939)
or we could just not publicly delegate a defacto private space?

Search domain is handy but it's ambiguous.

Re:New gTLD Application for .lan by _bernd on Saturday October 10, 2026 @04:34AM (#50030903)
I'm on that side that it was not a good idea right from the beginning. Because this problem exists in small enterprises since ages and the workaround always was to use a domain you own. At home I use home.arpa since 10 or 8 years or something.
Re:New gTLD Application for .lan by B1FF_PSUVM on Thursday October 08, 2026 @08:02PM (#50014153)
> use search domain

I don't know what this means, and searching is thorny. Help?

Re:New gTLD Application for .lan by denkmoon on Thursday October 08, 2026 @08:05PM (#50014174)
https://en.wikipedia.org/wiki/Search_domain

Your DHCP/SLAAC RA tells clients "here is a list of search domains, when you attempt to query a bare name, also look for the name plus any suffixes listed in the search domain list". So on a system with "home.arpa" in the search domains, you can do something like 'ping myhost' and your system should attempt to resolve 'myhost.home.arpa'.

Re:New gTLD Application for .lan by B1FF_PSUVM on Thursday October 08, 2026 @09:42PM (#50014970)
Thanks, appreciated. Forgot that wiki is good at this (and TV series ;-)
Re:New gTLD Application for .lan by _bernd on Saturday October 10, 2026 @04:32AM (#50030894)
Next time may narrow down the search space and look for those keywords combinend. The DHCP spec includes the search domain so it's not that hard to find and follow. Of course without any context this search would be not reveal anything useful.
Re:New gTLD Application for .lan by deno on Friday October 09, 2026 @07:36AM (#50019062)
So now you’re potentially in conflict with ALL gTLDS? I don’t get what this is supposed to accomplish.