On Sat, Nov 5, 2016 at 7:11 AM, Louis Lagendijk <louis@xxxxxxxxxx> wrote: > It is a best practice to leave .local for mDNS. Even Microsoft > recommends now against using .local https://en.wikipedia.org/wiki/.loca > l offers some good information on the subject. > > And for DNS-domains you better use only officially registered domains, > do not invent your own domain names. Somebody may register the TLD you > invented. Or the IETF might define it for some special purpose. > > I heard of a DSL-modem vendor that used .box for local names. And guess > what: somebody registered .box as an official top level domain.... > > Let the OP register an own domainname somewhere (or use a subdomain > under a dynamic DNS name), so that the domain is somewhat formally > owned. the disadvantage of the latter option is that it gives you a > pretty long domain name <my-server>.<user name>.ddnsprovider.org > Louis I think there should be a TLD that ICANN specifically excludeds from registration or use on the Internet but specifically allows private use. There are many scenarios were you might want to create a private network but not register or use an Internet domain name because it will never be exposed to other networks. This includes test domains, networks that are isolated for security reasons [1] and for personal home networks. Mike [1] DNS does not provide security but using a separate namespace may be required to completely isolate a network (eg if subdomain used, HTTP clients may submit cookies) _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
