[dns-operations] TLD(s) for private use
davew at hireahit.com
Wed Sep 6 17:23:38 UTC 2017
On 2017-09-06 05:22, James Stevens wrote:
>> No, the "correct" (or at least recommended) procedure is to use a
>> subdomain of one of your domains
> The "fear" I have with this technique is that there is the /potential/
> for the data to get out into the public domain, as its hosted in a
> publicly accessible TLD.
> A TLD that is not in the ROOT zone gives an added level of comfort -
> especially for those higher up the management chain for whom an
> understanding of the DNS might be less clear.
> Like others (e.g. RTBL), I have often used DNS to provide one-way data
> propagation. Its lightweight and has great facilities for live or polled
> updating - but it may be carrying data that I wouldn't want in the
> public domain.
You could simply buy a domain, assign no (external) nameservers at all,
and use it without fear of any conflict. This is the only safe option
that doesn't rely on third parties to be consistent over time.
More information about the dns-operations