148 points mzajc 1 month ago 162 comments
mzajc 1 month ago | parent
Regarding that last point, I've had issues with dnsmasq in the past where it was remotely resolving domains even when they were configured to resolve locally. For .lan domains, this could be disastrous because I often send plaintext traffic to them. I did submit a fix/workaround[0], but it's still something to look out for. If anyone knows more about this issue or other ways queries could leak, please share!
gclawes 1 month ago | parent
c0l0 1 month ago | parent
I hope the gTLD application gets struck down.
pwdisswordfishq 1 month ago | parent
c0l0 1 month ago | parent
free_bip 1 month ago | parent
jamesnorden 1 month ago | parent
stop50 1 month ago | parent
throw0101a 1 month ago | parent
* https://en.wikipedia.org/wiki/.internal
Other special use domains:
* https://en.wikipedia.org/wiki/Special-use_domain_name
* https://en.wikipedia.org/wiki/Top-level_domain#Reserved_doma...
jasomill 1 month ago | parent
Personally, I just use a registered domain for this purpose, as they're cheap enough to not care (last I checked, I pay $10–20/domain/year for registrations, depending on registrar and TLD, and $0.21/zone/month for hosting public zones on Google Cloud).
simondotau 1 month ago | parent
pqb 1 month ago | parent
[0]: https://amplifi.com/
simondotau 1 month ago | parent
lxgr 1 month ago | parent
esskay 1 month ago | parent
lokoj 1 month ago | parent
penskymaterial 1 month ago | parent
brookst 1 month ago | parent
GuB-42 1 month ago | parent
- 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.
joquarky 1 month ago | parent
simondotau 1 month ago | parent
denkmoon 1 month ago | parent
I can't fucking _wait_ to type bender.home.arpa instead of bender.lan. Hyped.
_bernd 1 month ago | parent
denkmoon 1 month ago | parent
Search domain is handy but it's ambiguous.
_bernd 1 month ago | parent
B1FF_PSUVM 1 month ago | parent
I don't know what this means, and searching is thorny. Help?
denkmoon 1 month ago | parent
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'.
B1FF_PSUVM 1 month ago | parent
_bernd 1 month ago | parent
deno 1 month ago | parent
Palomides 1 month ago | parent
gumby 1 month ago | parent
You may be confusing it with the IETF’s policy.
In early days of the RFCs, most started out as proposals, often but not always with some existing implementation as a jumping-off point to conversation (hence the name). I no longer remember why they started to be numbered and tracked, as the process naturally preceded that.
You can verify what I say by just reading some old ones at the rfc editor site.
gavinsyancey 1 month ago | parent
- Originally, IETF specified .home, but never went through the process to add it to the list of reserved names.
- Someone applied for the .home gTLD, and while it ultimately didn't go through there was a while while it was up in the air. Due to this the homenet working group had to change gTLDs.
- They decided to switch to .homenet. However, because of DNSSEC, whatever they used would need an insecure delegation in the root zone or validating resolvers wouldn't be able to resolve it. Since IAB controls .arpa but IANNA controls the root and there was no process to ask IANNA for this, they eventually decided to use home.arpa instead.
https://mailarchive.ietf.org/arch/msg/homenet/8cfJkr7SPMaPS4...
RFC 8244 is an interesting read on the topic: https://datatracker.ietf.org/doc/rfc8244/
fridder 1 month ago | parent
greatgib 1 month ago | parent
It should be logical even without thinking that the request have to be rejected.
brookst 1 month ago | parent
montecarl 1 month ago | parent
It was funny, because when I brought it up to them, it was hard to articulate why it was a problem and I couldn't convince them it was worth the effort of trying to fix. They never ran into a specific issue due to this while I was there but it felt so gross.
irusensei 1 month ago | parent
penskymaterial 1 month ago | parent
jasomill 1 month ago | parent
Historically (20+ years ago), some Microsoft documentation suggested .local as an example of an unregistered domain that could be used for this purpose, which was problematic when .local was subsequently reserved for multicast DNS.
yencabulator 4 weeks ago | parent
deno 1 month ago | parent
At least that's the conclusion I've arrived at at some point, but I don't remember what was the exact use case anymore.
However there are still several global IPv4 ranges that are not local reserved ranges but are effectively reserved and you could use them if you really want to without any issues.
masfuerte 1 month ago | parent
Brian_K_White 1 month ago | parent
Sure one day your printer might start spewing random json code meant for some microservice of the rightful IP owner.
Sure the IP's might be owned by the Air Force and one day they might start getting traffic from your pos ipad that they decide looks like an attempt to attack one of their internal secret networks...
Sure one day traffic meant to go to your printer ends up flooding and dossing a windmill controller, preventing the rightful operators from turning it the right direction during bad weather and causing $25M damage...
And of course the real failures are more like, only people from the Maldives can't send email to your email server, a failure with no impact.
antonkochubey 1 month ago | parent
jasomill 1 month ago | parent
ButlerianJihad 1 month ago | parent
Therefore, people who weren't on the Internet yet, or didn't expect to be connected to any particular WAN, or even had their own intranet WAN without public access, they improvised like crazy. Like, whatever IP address ranges worked for them, they just plugged 'em in.
Since it was indeed early, and IPv4 networks were being handed out like candy, the savvy companies just applied for their own network space, hopefully of an appropriate size. The applications at the time didn't specify or require that they route the traffic or put it into BGP, so registering your intranet with IANA was the right thing to do, and future-proof. Unfortunately, in the wild-west early days before CIDR, IANA needed to find either a chunk of class C, or class B without significant nuance. And that is how Apple, HP, and Ford came to control gigantic swaths of "Class A" space.
Renumbering private networks was one of the nightmare scenarios of consulting firms like mine. And it hasn't really stopped, I suppose. If your company does an M/A their private LANs may clash, and they either renumber or they NAT.
By the way, OpenWRT isn't supposed to be using ".lan". That's a ridiculous non-compliant behavior. Someone should've stopped that, long ago.
There are ways to subdomain properly and IETF has provided dedicated TLDs for it even now, but back in the day, it was not easy, and I get it. When I needed DNS for my homelab, I discovered that the best practice among bad practices was to subdomain your ISP's. Like, make up a fictitious subdomain and hang it off their real one. Then your DNS had an anchor in reality, even if it was all made up, never delegated, unreachable, unresolvable from the outside.
gavinsyancey 1 month ago | parent
https://icannwiki.org/Name_Collision_Risk_Management_Framewo...
simondotau 1 month ago | parent
This test is poorly designed for .lan because the opposite problem is more likely: that many people using .lan will have any resolution attempts swallowed by their routers. This is certainly true for OpenWrt and GL.iNet. It may be true for Unifi AmpliFi, which reserves .lan by default. It's potentially true for other vendors when .lan is configured as the local domain (which many online guides suggest people do).
lxgr 1 month ago | parent
Arguably that's on them, but .lan seems much more controversial and I really hope ICANN does the right thing here and at least declares it permanently reserved/non-registerable.
Once that happens, browsers and other stakeholders could then consider allowing self-signed TLS certificates, maybe with TOFU semantics, for .lan hosts, ideally together with .local mDNS ones.
slartibardfast0 1 month ago | parent
i can't understand why AVM don't allow this to be configured!
vekntksijdhric 1 month ago | parent
seanw444 1 month ago | parent
jstarks 1 month ago | parent
alerighi 1 month ago | parent
To me is a very bad idea to implement this proposal, it should instead be standardized and reserved for internal usage as a fix. There were even RFC like https://www.rfc-editor.org/info/rfc6762/#appendix-G that suggested their usage for local devices in a network.
What is the point of selling the .lan domain, except for making money at the expense of a security risk for millions of networks that already use that domain for internal hosts?
BTW to me there was never any sense to add new TLD domain despite country code. They decided to render internet less secure, by giving scammers infinite TLD to register they scam domain like "apple.lan", with the sole purpose of making for them easy money.
denkmoon 1 month ago | parent
gavinsyancey 1 month ago | parent
account42 1 month ago | parent
davidcollantes 1 month ago | parent
john_strinlai 1 month ago | parent
it is not, as .local is designated as a special-use domain name and .lan is not.
gertrunde 1 month ago | parent
It may not be an official standard, but it does have some weight as a de-facto standard.
I've tried briefly to try and find some numbers to back that up, but can't find much beyond apple's bonjour vs consumer routers - although I've seen companies with AD domains using .lan as well. (Although, I've also seen companies using 1.0.0.0/8 for their internal addressing...)
john_strinlai 1 month ago | parent
denkmoon 1 month ago | parent
john_strinlai 1 month ago | parent
if you choose to use an unreserved domain, you are choosing to accept the risk of something like this happening. take ownership of your choices. "but other people use it" is not a great defense.
queenkjuul 1 month ago | parent
john_strinlai 1 month ago | parent
gertrunde 4 weeks ago | parent
As an example, at one point in the past (I think in the 90's?), Microsoft recommended using .local for AD domains, whereas now they explicitly recommend against it.
simondotau 1 month ago | parent
jeroenhd 1 month ago | parent
irusensei 1 month ago | parent
procone 1 month ago | parent
.home.arpa is so clunky. Why do I have to put the acronym of a US military project in my domain to access resources on my own local network?
Yes, I know that organization was central to the development of the l Internet, but it's not relevant as a domain 40 years later.
john_strinlai 1 month ago | parent
irusensei 1 month ago | parent
procone 1 month ago | parent
This is not how anything should work.
sieve 1 month ago | parent
0x457 1 month ago | parent
lxgr 1 month ago | parent
I've been bitten by this with my home router which uses <device>.fritz.box when somebody registered fritz.box.
dwedge 1 month ago | parent
sybercecurity 1 month ago | parent
Also see a .bldg application, which also might conflict with some legacy naming schemes.
alwa 1 month ago | parent
The bureaucracy seems precision-engineered to stultify, but apparently the public have 104 days after “String Confirmation Day” (17th Nov; capitalization theirs) to lodge objections, assuming the “GAC” doesn’t beat them to it…
https://newgtldprogram.icann.org/en/application-rounds/round...
…of course there’s a “filing fee,” priced in “hours of a panel of lawyers’ time,” to lodge such an objection…
https://newgtldprogram-2026-agb.icann.org/en/8-module-4-comm...
…welp, hope somebody more organized (and better-funded) than I can organize an objection. Much as I feel like I’m giving up my right to gripe by assuming somebody else will come along to do the weeding.
ZeroWidthJoiner 1 month ago | parent
This may very well end up to be determined too risky to be delegated, like .corp, .home and .mail in 2018.
gavinsyancey 1 month ago | parent
- "String Confusion" -- looks or sounds like an existing (approved or being applied for) gTLD. Must be filed by whoever owns (or is applying for) that gTLD.
- "Legal Rights" -- someone else owns a trademark this would violate. Must be filed by whoever's legal rights would be violated.
- "Limited Public Interest" -- the gTLD is immoral under recognized principles of international law. I have no idea when this could be applicable.
- "Community" -- An established community organization believes the group this gTLD is intended to target will object to it. This seems more like a vehicle for e.g. Little People of America to let ICANN know that ".midget" would be offensive.
Unfortunately there doesn't seem to be a way to tell ICANN that .lan has been widely used and will break things in a way they will listen to.
simondotau 1 month ago | parent
ICANN isn't the DNS police, and lobbying them is pointless. We should campaign for open-source router projects[0], commercial hardware developers[1], DNS resolver developers, and major providers[2] to collectively designate commonly used private TLDs such as .home, .lan, .intranet, and .private as non-resolvable in public DNS.
Local resolution would continue to work, but these names would never be forwarded upstream. With sufficient adoption, we'd establish a de facto reservation and make the TLDs commercially worthless, regardless of what ICANN decides.
--
[0] There is precedence here. OpenWrt already reserves .lan in its default dnsmasq configuration.
[1] There is precedence here. GL.iNet inherits from its OpenWrt roots. Ubiquiti uses .lan as the default in its AmpliFi products. MikroTik documents it as part of its network-discovery mechanism.
[2] I'm thinking of Cloudflare, Quad9, and others.
mzajc 1 month ago | parent
ICANN and IANA very much are the DNS police. As a matter of fact, IANA maintains a list of special-use domains - though, despite its widespread use, .lan is not on the list - and these domains will get rejected from gTLD applications outright. The last thing I want is to require each recursive resolver to have their own idea of what should and shouldn't be resolved.
On a related note, Google owns a registry (CRR) and a recursive resolver (8.8.8.8) that's commonly used by default or as fallback. Letting them ban entire TLDs would be a massive conflict of interest.
simondotau 1 month ago | parent
What I implied (but failed to emphasise) is that what I'm calling for is already in de-facto effect, with multiple software and hardware vendors treating .lan as not publicly resolvable. What you describe as "the last thing [you] want" is already happening; my proposal is for more of the same.
It is valid to note that ICANN could abuse their contractual arrangements with resolvers who also operate registrars, but this would be an illegal intimidation tactic. It would not be a conflict of interest for Google to act if part of a wider campaign involving other parties.
denkmoon 1 month ago | parent
Community groups can make their own competing DNS hierarchy and governing body and perhaps should but I don't think saying ICANN aren't responsible here is reasonable.
simondotau 1 month ago | parent
Formal objections require standing, procedural compliance and fees. Demanding monetary payment in order to issue an objection means that ICANN not acting as a responsible party in my view.
account42 1 month ago | parent
simondotau 1 month ago | parent
The most valuable parties to sway wouldn't even be Google or Cloudflare. As registrars as well as resolvers, I've no serious expectation that they'd stick their neck out. Ubiquiti might though.
unleaded 1 month ago | parent
vetrom 1 month ago | parent
Source: the application refers to multiple layers of LLC ownership, and the responsible parties listed are general counsels at some IP financialization company, "Identity Digital"
hdgvhicv 1 month ago | parent
p1mrx 1 month ago | parent
Faelian2 1 month ago | parent
Having internal domain names owned by some guy on the internet has already compromised multiple corporate networks. See the talk from this guy:
https://www.romhack.io/wp-content/uploads/2025/10/Internal-D...
john_strinlai 1 month ago | parent
at the very least, the .dev stuff should have had people second-guessing their usage of unreserved domains.
gchamonlive 1 month ago | parent
In time we'll see articles like "Don't register a .lan domain if you want people to visit your site"
delecti 1 month ago | parent
john_strinlai 1 month ago | parent
throughout most of my career, there was no unreserved domain that felt safe. but especially after .dev.
kokx 1 month ago | parent
That leaves .home.arpa, which is very awkward and only a thing since 2018 (my home network's use of .lan definitely predates this). Especially as a non US citizen. It also seemed so far that .lan was the "unofficial" gTLD to be used, since much software like OpenWRT was already using it anyway.
Either way: making .lan internet routable seems entirely unhinged to me. LAN has always been the acronym for Local Area Network. Why would anyone sane think that it is a good idea to make this into a gTLD that can be internet routable? The only way I see forward to do this justice, is to only allow RFC 1918 and IPv6 addresses that are within the assigned prefix for your router.
This seems like a worse version of allowing .zip to be a gTLD. Remember the idea of downloading something from https://github.com/[...]@evil.zip?
john_strinlai 1 month ago | parent
there is. it's .internal.
https://en.wikipedia.org/wiki/.internal
(note: i hope .lan does not get approved, but people have to understand that they are rolling dice when using unreserved names)
edit: fucking wild that this is downvoted into negatives. press the wiki link and read the first line if you don't believe me. in fact, i will quote it: "The name internal is reserved by ICANN "
kokx 1 month ago | parent
That explains why I hadn't heard of this yet. My current incarnation of my internal network dates from ~april 2024.
simondotau 1 month ago | parent
gucci-on-fleek 1 month ago | parent
.qm to .qz and .xa to .xz have always been implicitly reserved as TLDs that will never be globally-routable [0] [1], but these aren't exactly the most intuitive names so it's unsurprising that nobody uses them.
(".internal" as mentioned by the sibling comment [2] is the best choice these days, but its definition is somewhat recent.)
[0]: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#User-assign...
[1]: https://en.wikipedia.org/wiki/Country_code_top-level_domain#...
srcreigh 1 month ago | parent
akerl_ 1 month ago | parent
Home.arpa exists, or buy a domain and use that. Or pick something that’s not reserved and run the risk of this happening.
steventhedev 1 month ago | parent
deno 1 month ago | parent
FTFY
stackskipton 1 month ago | parent
Even today when setting up greenfield networks, I generally use internal.company.com. It also lets you get public trusted SSL certificates so you don't have to deal with internal PKI.
Faelian2 1 month ago | parent
john_strinlai 1 month ago | parent
procone 1 month ago | parent
There's almost no value.
Large businesses almost never use them. The potential for scams / phish / etc are now limitless.
SahAssar 1 month ago | parent
simondotau 1 month ago | parent
It's arguably defensible to have a limited number of non-geographic TLDs. "Dot com" was an aesthetic as much as a technical decision. I wonder though, if .com/net/org had never existed, we would have a different sense of aesthetic around domain names, and there's no reason to think that it would be any better or worse than what we have now.
deno 1 month ago | parent
Fortunately there’s no need to speculate as the application explains this clearly:
AGB Q118: What is the meaning/definition of the applied-for gTLD string?
Answer: Lan commonly refers to a broadly recognized term used across a wide range of contexts.notpushkin 1 month ago | parent
Group_B 1 month ago | parent
dijit 1 month ago | parent
For those not in the know, Google lobbied ICANN to get the name and in their application they stated (repeatedly) that the intent was to buy it so that it could be reserved; as .dev was already used by developers and if someone bought it for commercial purposes it would harm the developer community.[0]
.... they then proceeded to start selling them.
Leading to all kinds of issues, the exact issues that they raised...
https://github.com/basecamp/pow/issues/397
https://github.com/laravel/valet/issues/433
https://danielbachhuber.com/switch-laravel-valet-from-dev-to...
https://community.localwp.com/t/dev-domain-doesnt-work/4277
https://forums.theregister.com/forum/all/2017/11/29/google_d...
[0]: https://gtldresult.icann.org/applicationstatus/applicationde...
xd1936 1 month ago | parent
denkmoon 1 month ago | parent
akerl_ 1 month ago | parent
0x0 1 month ago | parent
montjoy 1 month ago | parent
ChrisArchitect 1 month ago | parent
ICANN Reveals 2026 Round Applications for New Generic Top-Level Domains
saghm 1 month ago | parent
moecables 1 month ago | parent
gavinsyancey 1 month ago | parent
yonatan8070 1 month ago | parent
gertrunde 1 month ago | parent
I'm guessing that'll end up being expensive for someone...
ectospheno 1 month ago | parent
yegle 1 month ago | parent
My tweet on Sep 26, 2026
gertrunde 1 month ago | parent
There are questions that literally say as part of the question "Choose Yes or No", so they've answered "true"...
And Q165 is fun: "Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused?" Answer: "No"
OutOfHere 1 month ago | parent
childintime 1 month ago | parent
It's monopolies like Verisign (of the .com tld) that have luxurious profits. No competition, plus they are allowed to raise their prices above inflation while their infrastructure costs go down every year.
"America" has our best interests at heart /s
akerl_ 1 month ago | parent
phs318u 1 month ago | parent
https://www.icann.org/en/board-activities-and-meetings/mater...
gavinsyancey 1 month ago | parent
phs318u 1 month ago | parent
.internal is all about the boundary between inside and the public internet, regardless of how you define ‘inside’.
gavinsyancey 1 month ago | parent
tvbusy 1 month ago | parent
yonatan8070 1 month ago | parent
I don't really see what website would use it though. Maybe for networking companies like mikrotik.lan or self hosted services like immich.lan?
sidneythekidney 1 month ago | parent
dwedge 1 month ago | parent
wolttam 1 month ago | parent
LtdJorge 1 month ago | parent
miladyincontrol 1 month ago | parent
iaaan 1 month ago | parent
yonatan8070 1 month ago | parent
> Objections for this Application have not yet been published. Information will be added when it becomes available. Please check back periodically for updates.
How does this work? Who can submit an objection? Can I submit one as someone with .lan domains inside my home network?
cloudie78 1 month ago | parent
Just purely from common sense perspective why the fuck should .lan be something that’s an internet/public TLD? Hello? LOCAL Area Network?
While we’re at it let’s update a few RFCs. Plus I don’t want to find out what organisations use .lan for their networks and what will end up leaking to the internet as a consequence of this.
m-p-3 1 month ago | parent
randerson 1 month ago | parent
yencabulator 4 weeks ago | parent
> AGB Q118. What is the meaning/definition of the applied-for gTLD string?
> Lan commonly refers to a broadly recognized term used across a wide range of contexts.
> 1. Describe the mission and purpose of the applied-for gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose.
> The mission of .LAN is to provide a namespace associated with the applied-for string.
yencabulator 4 weeks ago | parent