Top
Best
New

Posted by nh2 10/24/2024

Chromium uses web search for .internal TLD instead of opening URL(issues.chromium.org)
116 points | 85 commentspage 2
walrus01 10/24/2024|
Also a good argument for, if you run internal-network only resources, to purchase and use an actual domain for it (such as companyname.us or whatever).

Publish a zone file for the domain as authoritative master and secondary on an internet facing DNS server, but have basically no records in the zone (no useful A or CNAME or anything else).

Host the actual DNS for your internal services on your internally-accessible-only DNS server.

notpushkin 10/24/2024|
Also can use DNS validation with Let’s Encrypt this way!
benatkin 10/24/2024||
I gotta say, I didn't like when Google grabbed .dev, but now I like having a .dev domain =)
oezi 10/24/2024|
Dev is HSTS preloaded and thus can't be used for internal http services as .internal can.
mproud 10/24/2024||
Per Wikipedia:

> As of October 18, 2024, the domain has not been standardized by the Internet Engineering Task Force (IETF), though an Internet-Draft describing the TLD has been submitted.

racked 10/24/2024||
Having trouble not attributing to malice that which is adequately explained by stupidity here...

For Home Assistant for instance, the only reasonable option is .internal - its default .local is not the right TLD to use. [1]

[1]: https://serverfault.com/a/937808

wkat4242 10/24/2024||
Isn't .local specific to 'rendezvous' tech anyway? I forget the generic name but it was Apple that put it on the map under this name. But I mean that serverless broadcast protocol.

What I do is I just bought a domain and use that together with DNS-based SSL. It's a bit hard to set up with every different SSL server but it's doable.

ethersteeds 10/24/2024|||
The non Apple name is multicast DNS or mDNS. mDNS is exclusive to .local, but not necessarily the other way around. From its Wikipedia entry:

"By default, mDNS exclusively resolves hostnames ending with the .local top-level domain. This can cause problems if .local includes hosts that do not implement mDNS but that can be found via a conventional unicast DNS server. Resolving such conflicts requires network-configuration changes that mDNS was designed to avoid."

aragilar 10/24/2024||
Per https://www.iana.org/assignments/special-use-domain-names/sp... and https://www.rfc-editor.org/rfc/rfc6761.html .local. is only for mDNS, but as with any other name you can always misuse it (see .corp. .dev. etc.).

I notice .alt. now exists.

aspenmayer 10/24/2024||||
There’s mDNS, zeroconf, and Bonjour.

https://en.wikipedia.org/wiki/.local

lathiat 10/24/2024|||
Rendezvous = Bonjour = Multicast DNS Service Discovery
notpushkin 10/24/2024|||
> its default .local is not the right TLD to use

What if you advertise it on mDNS?

bmacho 10/24/2024||
Hanlon's razor is malicious. Assuming malice is the trivial right choice. Assuming stupidity just bc it rhymes, or bc you can feel smart about yourself is stupid.
zx8080 10/24/2024||
Is the motivation known for this change? Any clue from commit history?
jsnell 10/24/2024|
There has not been a change, it's always worked like this. ICANN only reserved *.internal for use in internal networks a few months ago.
notpushkin 10/24/2024||
This. I suppose they use a list of TLDs to check if something looks like a domain, and .internal is not on the list and needs to be hardcoded.
AbuAssar 10/24/2024||
safari also does the same thing
deisteve 10/24/2024|
[dead]