On 01.09.2017 21:47, Tony Finch wrote:
Walter H.<walte...@mathemainzel.info> wrote:but there still doesn't exist any for company networks,The point of the homenet name is to provide a zero-configuration namespace for consumer devices.
ACK
BUT this need not necessarily be a public domain ..., just think of Active Directory Domains ...Corporate environments are a somewhat different matter, since you can expect them to own their own domain name and have people who can set up devices to use it.
such a registry where you can register domains for internal use doesn't exist ... not one registry is willing to give me a domain - even when I pay for this - which I only use in a LAN,Internal networks should either use a subdomain of the company's public domain, or register a second domain for internal use.
and the authoritativ DNS servers would then just be 127.0.0.1 or ::1there is a security reason why companies often use .local for this case ..., but since RFC 6762 this conflicts ...
so there is the need of a TLD a company can use without conflicting ...
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop