3 ms·

.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...
  - wlonkly 2y ago
    But that's an IETF standard, not an ICANN policy. AFAIK there's nothing in place today that would _prevent_ ICANN from granting .local to a registry other than it just being a bad idea.
    - anderskaseorg 2y ago
      The jurisdictional status of .local and other standards-reserved special use domains is explained by RFC 6761 section 3: https://datatracker.ietf.org/doc/html/rfc6761#section-3 https://datatracker.ietf.org/doc/html/rfc6761#section-3 And ICANN is bound by the IETF/ICANN Memorandum of Understanding Concerning the Technical Work of the IANA, which prevents it from usurping that jurisdiction: https://www.icann.org/resources/pages/agreements-en https://www.icann.org/resources/pages/agreements-en
  - deleted 2y ago
    [deleted]
- throw0101d 2y ago
  > .local is in this weird state where it's _technically_ not reserved […] I doubt ICANN will actually touch .local, but they could. It is. See §2.2.1.2.1, "Reserved Names", of ICANN's gTLD Applicant Guidebook: * https://newgtlds.icann.org/sites/default/files/guidebook-full-04jun12-en.pdf https://newgtlds.icann.org/sites/default/files/guidebook-ful...
  - jeroenhd 2y ago
    This document describes the process for requesting gTLDs. Some internal ICANN project could ignore the contents of the guidebook without breaking "the rules". Or they could invent some kind of new TLD system; branded gTLDs didn't exist twenty years ago and I doubt most people would've assumed them to become real, yet blog.google is a real thing that exists.
- abtinf 2y ago
  > but they could. Presumably, ICANN, like any other committee, is not interested in self-castration. Which is what would happen if they challenged Apple. ICANN could do anything with enough rule changes. And then everyone will ignore them.
mjevans 2y ago
Give Apple / mDNS .mdns and let it use THAT instead of .local which should NEVER have been taken from local use in the first place.
- duskwuff 2y ago
  mDNS (which isn't just an Apple thing) has been using .local for roughly 20 years now. It's a little late to change that.

.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...
- wlonkly 2y ago
  But that's an IETF standard, not an ICANN policy. AFAIK there's nothing in place today that would _prevent_ ICANN from granting .local to a registry other than it just being a bad idea.
  - anderskaseorg 2y ago
    The jurisdictional status of .local and other standards-reserved special use domains is explained by RFC 6761 section 3: https://datatracker.ietf.org/doc/html/rfc6761#section-3 https://datatracker.ietf.org/doc/html/rfc6761#section-3 And ICANN is bound by the IETF/ICANN Memorandum of Understanding Concerning the Technical Work of the IANA, which prevents it from usurping that jurisdiction: https://www.icann.org/resources/pages/agreements-en https://www.icann.org/resources/pages/agreements-en
- deleted 2y ago
  [deleted]
throw0101d 2y ago
> .local is in this weird state where it's _technically_ not reserved […] I doubt ICANN will actually touch .local, but they could. It is. See §2.2.1.2.1, "Reserved Names", of ICANN's gTLD Applicant Guidebook: * https://newgtlds.icann.org/sites/default/files/guidebook-full-04jun12-en.pdf https://newgtlds.icann.org/sites/default/files/guidebook-ful...
- jeroenhd 2y ago
  This document describes the process for requesting gTLDs. Some internal ICANN project could ignore the contents of the guidebook without breaking "the rules". Or they could invent some kind of new TLD system; branded gTLDs didn't exist twenty years ago and I doubt most people would've assumed them to become real, yet blog.google is a real thing that exists.
abtinf 2y ago
> but they could. Presumably, ICANN, like any other committee, is not interested in self-castration. Which is what would happen if they challenged Apple. ICANN could do anything with enough rule changes. And then everyone will ignore them.

mjevans 2y ago

Give Apple / mDNS .mdns and let it use THAT instead of .local which should NEVER have been taken from local use in the first place.

duskwuff 2y ago
mDNS (which isn't just an Apple thing) has been using .local for roughly 20 years now. It's a little late to change that.