On Mon, Sep 04, 2017 at 08:12:39AM +0200, Walter H. <walte...@mathemainzel.info> wrote a message of 23 lines which said:
> the 1st: uniqueness is not a requirement here Serious mistake. Companies merge, and are bought. Any netadmin had, at least once in his professional life, to manage RFC 1918 networks merging and collisioning after some corporate change. If it's not realistic to switch from .local to the proper .private.mycompany.com to follow Best Practices, then it is certainly not realistic to do so when two companies merge, and their .local collide. > the 2nd: global knowledge of locally used names might raise a > security problem ... You don't have to make the nameservers reachable from the outside. Most of the time, name servers for .private.mycompany.com are internal-only. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
