David Wright wrote: > On Wed 30 Sep 2026 at 17:28:27 (+0200), john doe wrote: > > On 9/30/26 5:18 PM, David Wright wrote: > > > On Wed 30 Sep 2026 at 10:53:38 (-0400), Stefan Monnier wrote: > > > home: 173 mail: 162 corp: 0 > > > > > > I haven't yet bothered to move to .home.arpa. Maybe sometime. > > > > > > > I'd suggest the internal TLD instead! ;^) > > $ grep -r '\<internal\>' /etc 2>/dev/null | wc -l > 85 > $ grep -r '\<home.arpa\>' /etc 2>/dev/null | wc -l > 0 > $ grep -r -l '\<corp\>' /etc 2>/dev/null > /etc/hosts > /etc/aliases > /etc/mailname > /etc/exim4/update-exim4.conf.conf > /etc/exim4/hubbed_hosts > $ > > So more false positives with internal, and still semi-official?
Actually official: .internal is a top-level label reserved by ICANN for private-use DNS namespaces that are not part of the global public DNS root. In July 2024, the ICANN Board resolved that .internal will never be delegated in the root zone, so that it can be used by organisations as a non-colliding private-use TLD. ... Unlike .local or .home.arpa, .internal is not registered as a Special-Use Domain Name under RFC 6761, and no special resolution behaviour is defined beyond the prohibition on root-zone delegation. It is therefore closer to a policy-reserved label, analogous in spirit to private-use IP address ranges described in RFC 1918 and the shared-address space in RFC 6598, but applied to the DNS namespace. https://icannwiki.org/.internal -dsr-
