On 2016-02-24 Wed 14:13 PM |, Kamil Cholewi??ski wrote:
>
> Any other relevant RFC's?
>
Yes Kamil;-
RFC 6761 (2606) reserves
*) .example: for use in examples, includes .example.{com,net,org}
*) .invalid: for use as obviously invalid
(@address.invalid has special meaning for MTAs,
for remote header rewrites)
*) .localhost: to avoid conflict with the traditional
use of localhost as a hostname
*) .test: for use in DNS tests
RFC 6762 reserves ".local" for link-local host names which can
be resolved via Multicast DNS. Hence confict with Apple stuff.
RFC 7686 registers ".onion" for providing access to end to end
encrypted, secure, anonymised services networks. Read: Tor nets.
".exit" is also related to Tor.
There were some others, such as ".oz" in Australia. Australians call
themselves "Aussies" (pronounced "Ozzies") hence .oz, & is now ".oz.au"
See also:
http://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml
Many SSL certificate issuers also (unoffically) recognise these:
.lan
.priv
.localdomain (which has been respected forever.......)
Such as:
https://www.tbs-certificates.co.uk/FAQ/en/normes_tld.html
https://support.ssl.com/Knowledgebase/Article/View/34/0/acceptable-internal-domain-names
https://support.comodo.com/index.php?/Default/Knowledgebase/Article/View/722/16/
Here's the full public domain name root list (which changes):
http://www.iana.org/domains/root/db
Bernstein writes "It isn't easy to choose a safe top-level local name.
The global root operators add new top-level names every once in a while:
for example, .info was added in 2001, so people using .info as a local
name were unable to reach global .info sites."
He suggests ".internal", which is what I deploy (see the headers).
http://cr.yp.to/djbdns/dot-local.html
Cheers.
--
Because of the savour of thy good ointments
thy name is as ointment poured forth,
therefore do the virgins love thee.
-- Song of Solomon
