I believe ICCAN are moving to possibly replacing .local, .home, .lan, .corp, .mail, .localdomain, (and possibly others) with .internal ?
How could this affect mDNS and the use of .local? https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024 Staff have assessed that there have been no responses that would cause them to view the analysis as erroneous or to require re-assessment or a different conclusion. Therefore the proposed selection (.INTERNAL), along with the outcome of the public comment proceeding, will be presented to the ICANN Board for further consideration. https://icannwiki.org/Name_Collision ICANN deemed two strings, .home and .corp, as "high-risk" because of the widespread use of the terms on internal networks. Currently, ICANN is indefinitely delaying the delegation of these string to the root. Public Comments 2. Case Studies of Collision Strings (.corp, .home, .mail, .internal, .lan, and .local) based on DNS query data from A and J root servers in light of DNS evolution. https://www.icann.org/en/system/files/files/name-collision-mitigation-01aug14-en.pdf ICANN has stated that it will indefinitely defer delegating three TLDs: .corp, .home, and .mail. These gTLDs are still in common use in private namespaces, and thus pose a significantly higher risk for collisions than other TLDs. The deferral is not guaranteed to be forever, so any organization using one of those names as a private namespace should still follow the directions in Section 4 or Section 5 for migrating from the private namespace. https://www.icann.org/en/system/files/files/name-collision-mitigation-01aug14-en.pdf https://www.theregister.com/2024/01/29/icann_internal_tld/ https://datatracker.ietf.org/doc/html/rfc6762 Using ".local" as a private top-level domain conflicts with Multicast DNS and may cause problems for users. https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-113-en.pdf https://wiki.archlinux.org/title/Systemd-resolved https://www.freedesktop.org/software/systemd/man/latest/nss-resolve.html