Re: [DNSOP] DNS names for local networks - not only home residental networks ...

["Paul Hoffman" <[e-mail]>]

On 3 Sep 2017, at 14:38, Mark Andrews wrote:

>> ]On 4 Sep 2017, at 4:47 am, Walter H. <[e-mail]> 
>> wrote:
>>
>> even if I fully ACK this, but 15 years ago, nobody said, that  
>> ".local", ... would conflict one day ...
>> and also the company I work for has decided at these times to use a 
>> ".local" as internal domain and AD;
>> now it is impossible to change this ...
>
> Why would anyone tell you that “.local” would conflict when you 
> were supposed
> to register a name *before* using it.

Because some vendors gave bad advice in their documentation, 
particularly in examples.

> That’s been the case since the very beginning.
> No one ever said there would not be new TLD’s registered.  You 
> gambled and you
> lost.

If an end-user follows advice from vendors, and the vendors turn out to 
be wrong, maybe statements like that are inappropriate.

> If you are doing AD correctly you should be able to register you 
> machines wherever
> they connect to the Internet and that requires a public registration.

And that is what Microsoft has suggested in all their documentation for 
many years.

--Paul Hoffman