5 ms·

Can we get .local or .l added for private-use applications too?

by csdreamer7 2y ago

kxrm 2y ago
Is it not already? https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local
- csdreamer7 2y ago
  Not by ICANN? https://www.iana.org/domains/root/db https://www.iana.org/domains/root/db
  - duskwuff 2y ago
    The ICANN root zone only contains gTLDs and ccTLDs which are delegated. Other TLDs which are explicitly reserved for non-public use, like .localhost, .test, or .invalid, don't appear on that list either.
    - csdreamer7 2y ago
      Ty for the information.
    - quectophoton 2y ago
      I think a more correct place to look at would be the gTLD Applicant Guidebook[1][2], section "2.2.1.2.1 Reserved Names", which I guess should be updated to now include "INTERNAL". Though that list apparently includes all reserved names, not only those reserved for non-public use. [1]: https://newgtlds.icann.org/en/applicants/agb https://newgtlds.icann.org/en/applicants/agb [2]: https://newgtlds.icann.org/sites/default/files/guidebook-full-04jun12-en.pdf https://newgtlds.icann.org/sites/default/files/guidebook-ful...
duskwuff 2y ago
.local is already reserved for mDNS.
- jeroenhd 2y ago
  .local is in this weird state where it's _technically_ not reserved, but most PCs in the world already resolve it with special non-DNS software because of the Bonjour/mDNS protocol. So you end up with the IETF standardising .local, because Apple was already using it, but ICANN never did much with that standardisation. I doubt ICANN will actually touch .local, but they could. One could imagine a scheme where .local is globally registered to prevent Windows clients (who don't always support mDNS) from resolving .local domains wrong.
  - arjvik 2y ago
    Modern windows supports mDNS these days!
    - jeroenhd 2y ago
      It does! I generally assume mDNS to just be available on every device these days. But I've also seen managed environments where mDNS has been turned off or blocked at the firewall.
      - dboreham 2y ago
        mDNS is a broadcast protocol so always "blocked at the firewall ".
        oasisbob 2y ago
        Multicast too. If you've never needed to manipulate ACLs for multicast traffic, you're not really living.
        deleted 2y ago
        [deleted]
  - candiddevmike 2y ago
    It's reserved per RFC 6762: > This document specifies that the DNS top-level domain ".local." is a special domain with special semantics, namely that any fully qualified name ending in ".local. https://datatracker.ietf.org/doc/html/rfc6762 https://datatracker.ietf.org/doc/html/rfc6762 Applications can/will break if you attempt to use .local outside of mDNS (such as systemd-resolved). Don't get upset when this happens. Interesting fact: RFC 6762 predates Kubernetes (one of the biggest .local violators), they should really change the default domain...
eddyg 2y ago
.home, .corp and .mail are on ICANN’s “high risk” list so won’t ever be gTLDs, so they are also good (short) options. Ref: https://www.icann.org/en/board-activities-and-meetings/materials/approved-board-resolutions-regular-meeting-of-the-icann-board-04-02-2018-en#2.c https://www.icann.org/en/board-activities-and-meetings/mater...
- NewJazz 2y ago
  They could be gTLDs in the far future, but ICANN is likely to hold off for a good long while. Better to use something that is actually reserved, though. You never know.
LeoPanthera 2y ago
Using .local causes big problems with mDNS/Bonjour/Rendezvous, which also uses that TLD.
mjevans 2y ago
Please also reserve .lan which is what I now prefer to use since .local got stolen from private networks.
- NewJazz 2y ago
  You can use .home.arpa. https://datatracker.ietf.org/doc/html/rfc8375 https://datatracker.ietf.org/doc/html/rfc8375
  - neop1x 2y ago
    You can use a public subdomain like box.uuid.california.usa.mydns.org but we need something short like .l or .lan :) .home.arpa is terrible. I have been using .l personally for a couple of years and it works fine except Chrome won't recognize it as a tld and would start a google search. Once it is visited a couple of times, it autocompletes it as a webpage so it's quite usable afterall.
    - deleted 2y ago
      [deleted]

Can we get .local or .l added for private-use applications too?

kxrm 2y ago

Is it not already? https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local

csdreamer7 2y ago
Not by ICANN? https://www.iana.org/domains/root/db https://www.iana.org/domains/root/db
- duskwuff 2y ago
  The ICANN root zone only contains gTLDs and ccTLDs which are delegated. Other TLDs which are explicitly reserved for non-public use, like .localhost, .test, or .invalid, don't appear on that list either.
  - csdreamer7 2y ago
    Ty for the information.
  - quectophoton 2y ago
    I think a more correct place to look at would be the gTLD Applicant Guidebook[1][2], section "2.2.1.2.1 Reserved Names", which I guess should be updated to now include "INTERNAL". Though that list apparently includes all reserved names, not only those reserved for non-public use. [1]: https://newgtlds.icann.org/en/applicants/agb https://newgtlds.icann.org/en/applicants/agb [2]: https://newgtlds.icann.org/sites/default/files/guidebook-full-04jun12-en.pdf https://newgtlds.icann.org/sites/default/files/guidebook-ful...

duskwuff 2y ago

.local is already reserved for mDNS.

jeroenhd 2y ago
.local is in this weird state where it's _technically_ not reserved, but most PCs in the world already resolve it with special non-DNS software because of the Bonjour/mDNS protocol. So you end up with the IETF standardising .local, because Apple was already using it, but ICANN never did much with that standardisation. I doubt ICANN will actually touch .local, but they could. One could imagine a scheme where .local is globally registered to prevent Windows clients (who don't always support mDNS) from resolving .local domains wrong.
- arjvik 2y ago
  Modern windows supports mDNS these days!
  - jeroenhd 2y ago
    It does! I generally assume mDNS to just be available on every device these days. But I've also seen managed environments where mDNS has been turned off or blocked at the firewall.
    - dboreham 2y ago
      mDNS is a broadcast protocol so always "blocked at the firewall ".
      - oasisbob 2y ago
        Multicast too. If you've never needed to manipulate ACLs for multicast traffic, you're not really living.
      - deleted 2y ago
        [deleted]
- candiddevmike 2y ago
  It's reserved per RFC 6762: > This document specifies that the DNS top-level domain ".local." is a special domain with special semantics, namely that any fully qualified name ending in ".local. https://datatracker.ietf.org/doc/html/rfc6762 https://datatracker.ietf.org/doc/html/rfc6762 Applications can/will break if you attempt to use .local outside of mDNS (such as systemd-resolved). Don't get upset when this happens. Interesting fact: RFC 6762 predates Kubernetes (one of the biggest .local violators), they should really change the default domain...

eddyg 2y ago

.home, .corp and .mail are on ICANN’s “high risk” list so won’t ever be gTLDs, so they are also good (short) options. Ref: https://www.icann.org/en/board-activities-and-meetings/materials/approved-board-resolutions-regular-meeting-of-the-icann-board-04-02-2018-en#2.c https://www.icann.org/en/board-activities-and-meetings/mater...

NewJazz 2y ago
They could be gTLDs in the far future, but ICANN is likely to hold off for a good long while. Better to use something that is actually reserved, though. You never know.

LeoPanthera 2y ago

Using .local causes big problems with mDNS/Bonjour/Rendezvous, which also uses that TLD.

mjevans 2y ago

Please also reserve .lan which is what I now prefer to use since .local got stolen from private networks.

NewJazz 2y ago
You can use .home.arpa. https://datatracker.ietf.org/doc/html/rfc8375 https://datatracker.ietf.org/doc/html/rfc8375
- neop1x 2y ago
  You can use a public subdomain like box.uuid.california.usa.mydns.org but we need something short like .l or .lan :) .home.arpa is terrible. I have been using .l personally for a couple of years and it works fine except Chrome won't recognize it as a tld and would start a google search. Once it is visited a couple of times, it autocompletes it as a webpage so it's quite usable afterall.
  - deleted 2y ago
    [deleted]