1876534 - ICANN is asking for input on new `.internal` TLD for use in private networks.

Status: RESOLVED DUPLICATE of bug 1877108

(Core :: Networking, task)

Description

[Simon Friedberger [:simonf]]

Saw this on the PSL issue tracker: https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024

We have some special casing for .onion and localhost which we might want to consider for this. Or we might want to exempt it from DoH if it uses a non-private external resolver.

I can't think of anything that might be problematic here since people have been ad-hoc using .home or .local for this.

Comment 1

[Simon Friedberger [:simonf]]

For .onion it seems we are currently

1. hiding it from referrer and origin headers
2. excepting it from HTTPS upgrades
3. allow it for secure context
4. excempt them from DNS lookups
5. allow them for OpenSearch

At least 3. & 4. should not apply.

Comment 2

[Valentin Gosu [:valentin] (he/him)]

While I think there are some important differences between .internal and .onion (mainly that internal is still supposed to use conventional DNS infrastructure) I agree with your suggestions.
Additionally I would add that we should avoid using DNS over HTTPS for .internal domains since they wouldn't resolve anyway.