3 ms·
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 full
by 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 agoBut 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 agoThe 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]