IETF Logo Mail Archive

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

Paul Wouters <paul@nohats.ca> Fri, 01 September 2017 19:58 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52BBC133085 for <dnsop@ietfa.amsl.com>; Fri, 1 Sep 2017 12:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6KdYwaplmBR for <dnsop@ietfa.amsl.com>; Fri, 1 Sep 2017 12:58:32 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9893D133079 for <dnsop@ietf.org>; Fri, 1 Sep 2017 12:58:32 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3xkVRS1DRGz21d; Fri, 1 Sep 2017 21:58:28 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1504295908; bh=o/pTJNIHw/+5ZNQ8o/ay0cYAQcrUjGp2AwAkm29SMDA=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=VQm8CIMd0ZsPy7JB0Q9FIedKLnsFmkger0Z3uQs/FZU8VXPidUsZC6pItEC4kI/Ki dq1GjvM4dmHyvQxIZ5jbasPNOpj1h+AotwHdOmHU7cy9yQlOgGW+KW4VH8q9BkhMh1 b9jLKM38A/fKwUy0cIESovoV/S/3G3Uq1+KdSOXQ=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id wpCDB4w_CIV6; Fri, 1 Sep 2017 21:58:27 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 1 Sep 2017 21:58:27 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id D41FE96F; Fri, 1 Sep 2017 15:58:25 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca D41FE96F
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id BC38840B8F46; Fri, 1 Sep 2017 15:58:25 -0400 (EDT)
Date: Fri, 01 Sep 2017 15:58:25 -0400
From: Paul Wouters <paul@nohats.ca>
To: "Walter H." <Walter.H@mathemainzel.info>
cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <59A9B760.2060209@mathemainzel.info>
Message-ID: <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/LDU0x0Ih7wHV4Zr-Rxhbq04rpkY>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 19:58:34 -0000

On Fri, 1 Sep 2017, Walter H. wrote:

> but there still doesn't exist any for company networks, they most commonly use
> the domain name 'local', which I already noticed, that this conflicts to RFC 6762 ...

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.

I think you might be confused, and see "local" domain stuff on your
enterprise network, eg mdns stuff. That is its own realm.

Paul

v2.23.0 | Report a Bug | By Email