[dns-operations] TLD(s) for private use

[James Stevens]

Do ICANN /guarantee/ to never allow an "incredibly offensive" TLD? ... 
the more you know!

Sadly, it might (instead) result in an invitation to find alternative 
employment!


On 06/09/17 11:56, Ian McDonald wrote:
> One could always make them incredibly offensive, though I’m not sure 
> that would result in less support calls than invalid..
> 
> Sent from my Windows 10 phone
> 
> *From: *James Stevens <mailto:James.Stevens at jrcs.co.uk>
> *Sent: *06 September 2017 11:32
> *To: *dns-operations at dns-oarc.net <mailto:dns-operations at dns-oarc.net>
> *Subject: *[dns-operations] TLD(s) for private use
> 
> Apart from those in RFC-6761, is there any TLD, or format of TLD, that
> can be used for private use that is guaranteed never to be allocated?
> 
> I'm guessing dot-ZZ might fit that criterion, on the basis no country
> will ever get it, but I was hoping for something that was a bit more
> officially endorsed.
> 
> Until now I've been using names with a "zz--" prefix, e.g. "zz--data.",
> more on the basis of probability of lack of future allocation, but would
> prefer to use something more official.
> 
> Or is the correct procedure to be using something like "data.invalid."?
> 
> I'm thinking of situations like using DNS to distribute data, or for the
> names of local LANs - I can envisage a lot of support calls if I used
> "invalid." for local LANs.
> 
> 
> 
> James
> _______________________________________________
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> dns-operations mailing list
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations