Re: [DNSOP] Glue is not optional, but sometimes it *is* sufficient...

John Levine <johnl@taugh.com> Thu, 21 May 2020 21:41 UTC

Return-Path: <johnl@iecc.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 312663A0C62 for <dnsop@ietfa.amsl.com>; Thu, 21 May 2020 14:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=e3MxMVxT; dkim=pass (1536-bit key) header.d=taugh.com header.b=LFLHdRjh
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 ywC9mzVgQphc for <dnsop@ietfa.amsl.com>; Thu, 21 May 2020 14:41:26 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 1ED853A0C5F for <dnsop@ietf.org>; Thu, 21 May 2020 14:41:25 -0700 (PDT)
Received: (qmail 59275 invoked from network); 21 May 2020 21:41:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=e788.5ec6f584.k2005; bh=qFg1Fkbqa9ETB3DWNwgLF47/uyyfTklENvsw/Pku2HQ=; b=e3MxMVxTxXbgHSELeT2oCyh9adtOi2GMdwq/zTiXQp3OAv8qKC2aRMnZNitWlRrjnPdQz1KnGsx7mpfRCb2KFZnjrI2pa2HwiYhFvCCS64jdu4MdUS7LhNUyIoUHEVgHr385d/4bfWME2l9ySw+JdrASIoTMeEgl3c2sAKqhHndkciDLOqD6coAgCqIb31eEI0auGpDaJikGCt7qv+JBMbJjvOIImvVyMEmunCOWnfQD78Lp0u/BfyBSBZGmNSyB
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=e788.5ec6f584.k2005; bh=qFg1Fkbqa9ETB3DWNwgLF47/uyyfTklENvsw/Pku2HQ=; b=LFLHdRjhk0UnBC+DKkQTdORl4ubksh7t0S2/5uZ28EUY0Qyw+mhsZS6E7dcz0bhfMb7Pwgsj/3xAKmgfz0pFztJ6/T7e6koI+63zSjxevuHEimNfrrqrINxzLA3TcBdwbhBbhDRnc4LgksQpHNPB0zRzZzKw/vSNN+I/daKOgSPKzMtKYsgnLCap7HFsPuLli6brJhokCLdwWpAvfuIdrm2dQWqYIFEjRoZeVNV7Ns5D9dHiQfoNYORASJlhJkEn
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 21 May 2020 21:41:24 -0000
Received: by ary.qy (Postfix, from userid 501) id 271EC197E0DF; Thu, 21 May 2020 17:41:23 -0400 (EDT)
Date: Thu, 21 May 2020 17:41:23 -0400
Message-Id: <20200521214124.271EC197E0DF@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <CAHw9_i+UsV9NkuPM4KYBZhO7_J78MkUEyVR3fr=vOX-vsjJeUA@mail.gmail.com>
Organization: Taughannock Networks
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/UFyBPTvJwFO0TRzr57APlD7eknE>
Subject: Re: [DNSOP] Glue is not optional, but sometimes it *is* sufficient...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 May 2020 21:41:29 -0000

In article <CAHw9_i+UsV9NkuPM4KYBZhO7_J78MkUEyVR3fr=vOX-vsjJeUA@mail.gmail.com> you write:
>What if you *only* have glue, and no authoritative answer / server?
>Can I register example.com, put in www.example.com A 192.0.2.1 as
>glue, and not bother with this whole annoying authoritative server
>thing?

Based on my recent analysis of TLD zones, yes if the zone is managed by
Afilias, or if you have friends at Nominet.  Otherwise not so much.

For wow4dns.com it looks pretty normal other than that your NS is lame.

Here's what's in this morning's .COM zone file, but I assume you've updated the NS since then:

WOW4DNS NS NS1.AUTH-SERVERS.NET.
WOW4DNS NS NS2.AUTH-SERVERS.NET.

Your registrar record and the live .COM NS say:

$ dig @g.gtld-servers.net. wow4dns.com a
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45456
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;wow4dns.com.			IN	A

;; AUTHORITY SECTION:
wow4dns.com.		172800	IN	NS	www.wow4dns.com.
wow4dns.com.		172800	IN	NS	www1.wow4dns.com.

;; ADDITIONAL SECTION:
www.wow4dns.com.	172800	IN	A	193.151.173.35
www1.wow4dns.com.	172800	IN	A	193.151.173.35

R's,
John