On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters 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
> On Sep 2, 2017, at 8:29 PM, Warren Kumari wrote:
>
> On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters 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 fi
On Sat, Sep 2, 2017 at 8:36 PM, Ralph Droms wrote:
>
> On Sep 2, 2017, at 8:29 PM, Warren Kumari wrote:
>
> On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters 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
Warren Kumari wrote:
On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters wrote:
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
Subject: Re: [DNSOP] DNS names for local networks - not only home residental
networks ... Date: Fri, Sep 01, 2017 at 10:01:38PM +0200 Quoting Walter H.
(walte...@mathemainzel.info):
> On 01.09.2017 21:47, Tony Finch wrote:
> > Corporate environments are a somewhat different matter, since you can
