IETF Logo Mail Archive

Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost

"John Levine" <johnl@taugh.com> Wed, 13 September 2017 16:34 UTC

Return-Path: <johnl@taugh.com>
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 B3A31132C32 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 09:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 07p66oJ-f-AK for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 09:34:19 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (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 1C4761321B6 for <dnsop@ietf.org>; Wed, 13 Sep 2017 09:34:18 -0700 (PDT)
Received: (qmail 50017 invoked from network); 13 Sep 2017 16:34:17 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 13 Sep 2017 16:34:17 -0000
Date: Wed, 13 Sep 2017 16:33:55 -0000
Message-ID: <20170913163355.1038.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Cc: peter.van.dijk@powerdns.com
In-Reply-To: <153C19CC-3120-466A-A158-A9833A2D17A1@powerdns.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Q2PLEU1PbPbdolh53-bOcq-zL6E>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
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: Wed, 13 Sep 2017 16:34:21 -0000

In article <153C19CC-3120-466A-A158-A9833A2D17A1@powerdns.com> you write:
>> I agree that localhost.<foo> pointing to loopback is generally asking
>> for trouble, but I am not at this point sufficiently confident that it
>> is never ever a good idea to say MUST NOT rather than SHOULD NOT.  I
>> can for example imagine ways that might make some kinds of debugging
>> easier.
>
>I would settle for SHOULD NOT. Can you elaborate on the debugging?

There is something strange going on with my remote server, and I use
localhost.mydomain so a little debugging server on my own computer
can steal state and see whats going on.

On the other hand, I could do this just as well:

gazornplotz.mydomain IN A 127.0.0.1

so never mind.  Still not sure I haven't missed something, though.

R's,
John

v2.23.0 | Report a Bug | By Email