On 06/05/2017 09:13 PM, Walter H. wrote:
Actually, that*IS* a problem. You should not be doing that. That is
quite likely the source of all your problems. That domain name is
reserved for a specific purpose and putting it in DNS will cause
conflicts.
Sorry, you're telling*BULLSHIT*; the TLD .local is exactly reserved for
this purpose ...
Actually, .local is reserved by RFC 6762 for resolution via multicast DNS:
https://en.wikipedia.org/wiki/.local
OP is using that domain in standard DNS, in violation of relevant standards.
RFC 2606 reserves .test, .example, .invalid, and .localhost, none of
which are recommended for use in private networks. RFC 7686 reserves
.onion for Tor hidden services. As far as I know, there are no TLDs
reserved for private networks. All users should use properly registered
domains for all DNS zones, private and public.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
