Re: dot internal and mDNS
On 3 Aug 2024 12:59 +0000, from andy@strugglers.net (Andy Smith):
>> I believe ICCAN are moving to possibly replacing .local, .home, .lan,
>> .corp, .mail, .localdomain, (and possibly others) with .internal ?
>
> home.arpa was defined by IANA in 2018. If they go ahead with
> .internal then I can only imagine it will be in addition to, not
> instead of, home.arpa.
The initial version of the relevant Internet Draft (as published Aug
2) doesn't even mention home.arpa, which seems like an oversight as
the intended use is very similar. Hopefully that will be corrected
before publication as a RFC.
https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-07-2024-en#section2.a
https://datatracker.ietf.org/doc/draft-davies-internal-tld/
https://www.ietf.org/archive/id/draft-davies-internal-tld-00.txt
.home was _specifically_ for HNCP (see RFC 7788; just as .local is
_specifically_ for mDNS) and RFC 7788 was updated by RFC 8375 (the
reservation of .home.arpa) to use the more generic .home.arpa as a
default.
Assuming that there are no late showstoppers for the reservation of
.internal, we will going forward have two officially recommended
choices for where to place internal, non-unique hostnames; namely
*.internal and *.home.arpa. The third alternative is to register a
globally unique domain name and use that as the root for one's
internal DNS names; doing so guarantees global uniqueness in DNS for
the fully qualified names.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
Reply to: