On 03.09.2017 02:29, Warren Kumari wrote:
On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters<p...@nohats.ca> wrote:On Fri, 1 Sep 2017, Walter H. wrote:If you are a company and you are using a hardcoded domain of "local", then you have been and still are, completely broken. The only fix is to rename your network.ACK and which non public domain name I can use for this that doesn't conflict now and will not conflict in the future?Something that's yours and not squatted. For example internal.mathemainzel.info. Please see the last three years of dnsops and homenet working group list archives.... perhaps the other way of looking at the last thirty three years of DNS is that people *do* actually want something like this, and that perhaps it is time to actually create something specifically for it.
just a simple question: why hadn't there been such at the very beginning, which could have prevented situations like the following:"a company gets the advice to use a ".local" as the internal domain and Active Directory; at these times nobody would have thought, that this could be a conflicting problem in the future ...;
and now it is impossible to change this ..." now telling an admin not to use ".local" is easy, but 15 years ago ...
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
