Closed yahesh closed 2 months ago
@yahesh the challenge is with the addition of .internal is that it will not be added to the root, by design. So the behaviour of localzone.xyz might still be materially different than the .internal TLD with respect to actual global reachability.
Worth considering this before pivoting.
@yahesh the challenge is with the addition of .internal is that it will not be added to the root, by design. So the behaviour of localzone.xyz might still be materially different than the .internal TLD with respect to actual global reachability.
Worth considering this before pivoting.
Yes, this has already been considered. Actual global reachability has never been relevant for the localzone.xyz
domain. It was always meant to be used internally only (i.e. in an internal split-horizon DNS setup).
localzone.xyz
was added in https://github.com/publicsuffix/list/pull/915 with the intention to introduce a domain that can be used for internal services across different organizations without the risk of collisions.With the latest board decision of the ICANN to finally reserve the
.internal
TLD for this specific use-case,localzone.xyz
is no longer needed and the use of.internal
is recommended instead.I therefore intend to have
localzone.xyz
lapse in the future. I already removed the corresponding_psl
record to indicate that this PSL entry should be removed.Sorry for the rollback and thank you very much for your hard work. 🙏