On Wed, Sep 28, 2016 at 11:27:20PM -0000, John Levine wrote:
> The codes AA, QM-QZ, XA-XZ, and ZZ are "user assigned" and will never
> be used for countries. Last year Ed Lewis wrote an I-D proposing that
> XA-XZ be made private use and the rest future use, but as far as I can
> tell it never went anywhere.
>
> I've been telling people that if they need a fake private TLD for their local
> network they should use one of those since it is exceedingly unlikely
> ever to collide with a real DNS name. Am I right?
The the ".invalid" TLD is reserved, and has been used for private
naming of domains that are sure to not be real domains either
internally or on the public Internet. I use:
address.invalid - added to bare mailbox names in inbound external email.
bcc.invalid - rewrite domain for (env recipient data) lossless Bcc copies of
email
discard.invalid - rewrite domain for addresses whose email gets dropped.
local.invalid - rewrite domain for local delivery when no real domain is
"local"
...
This is of course different from squatting on a TLD for naming
"real" private domains, and I see little justification for the
latter. Real 2LDs, 3LDs, ... are cheap, and why not use those
instead?
And for documentation we of course have ".example", "example.net",
...
--
Viktor.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
