Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-03.txt
Peter Koch <pk@TechFak.Uni-Bielefeld.DE> Sun, 05 December 2004 20:31 UTC
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06477 for <dnsop-archive@lists.ietf.org>; Sun, 5 Dec 2004 15:31:15 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id iB5IjiUD004065; Sun, 5 Dec 2004 10:45:44 -0800 (PST)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id iB5Iji0i004064; Sun, 5 Dec 2004 10:45:44 -0800 (PST)
Received: from mailout.TechFak.Uni-Bielefeld.DE (mailout.TechFak.Uni-Bielefeld.DE [129.70.136.245]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id iB5IjfL5004006 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for <dnsop@lists.uoregon.edu>; Sun, 5 Dec 2004 10:45:43 -0800 (PST)
Received: from grimsvotn.TechFak.Uni-Bielefeld.DE (grimsvotn.TechFak.Uni-Bielefeld.DE [129.70.137.40]) by momotombo.TechFak.Uni-Bielefeld.DE (8.12.11/8.12.11/TechFak/2004/05/05/sjaenick) with ESMTP id iB5IjdSG012138 for <dnsop@lists.uoregon.edu>; Sun, 5 Dec 2004 19:45:39 +0100 (MET)
Received: from localhost (pk@localhost) by grimsvotn.TechFak.Uni-Bielefeld.DE (8.11.7+Sun/8.9.1) with SMTP id iB5Ijci11525 for <dnsop@lists.uoregon.edu>; Sun, 5 Dec 2004 19:45:38 +0100 (MET)
Message-Id: <200412051845.iB5Ijci11525@grimsvotn.TechFak.Uni-Bielefeld.DE>
X-Authentication-Warning: grimsvotn.TechFak.Uni-Bielefeld.DE: pk owned process doing -bs
X-Authentication-Warning: grimsvotn.TechFak.Uni-Bielefeld.DE: pk@localhost didn't use HELO protocol
To: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-03.txt
In-reply-to: Your message of "Fri, 03 Dec 2004 20:16:31 EST." <41B10FEF.5070900@daimlerchrysler.com>
X-Organization: Uni Bielefeld, Technische Fakultaet
X-Phone: +49 521 106 2902
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11521.1102272337.1@grimsvotn.TechFak.Uni-Bielefeld.DE>
Date: Sun, 05 Dec 2004 19:45:38 +0100
From: Peter Koch <pk@TechFak.Uni-Bielefeld.DE>
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Peter Koch <pk@TechFak.Uni-Bielefeld.DE>
Kevin Darcy wrote: > No, this sentence describes a DNS entity that is (in the historical > terminology) master or slave for one or more zones (i.e. an > "authoritative name server"), yet supports recursive querying (i.e. an > "iterative resolver"). It's a combination of two different roles in a > single entity. I think the wording is fine as it stands. after re- and rere-reading the draft paragraph An example is the entity that accepts recursive queries, issues iterative queries as necessary to resolve the initial recursive query, caches responses it receives, and which is also able answer questions about certain zones authoritatively. Often called a "recursive name server" or a "caching name server", it is in fact an iterative resolver combined with an authoritative name server. I stand corrected. (editorial nit: is also able [to] answer questions) Terminology confusion is indeed ugly. There's an agreed upon list in draft-ietf-dnsext-dnssec-intro. > There's nothing wrong with doing explicit type NS queries in the course > of troubleshooting. Please make sure that any language deprecating > explicit NS type queries makes clear that it only applies to the > generation of such queries as part of the regular resolution process. Sure, sorry for being unclear in my remark. Debugging is of course out of scope. > >not necessary and shouldn't be introduced. > > > See Section 4 of RFC 2136. A Dynamic Update requestor is assumed to "be > able to determine the nameservers for th[e] zone" and to be able to > match an SOA MNAME with an NS NSDNAME. Such statements imply the > issuance of NS record type queries. It doesn't outlaw them but it also doesn't necessarily imply them since the NS RRs can also be learned from the authority section of a response to a query for another QTYPE, e.g. SOA. -Peter . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
- [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-03.t… Rob Austein
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Rob Austein
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Pekka Savola
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Andras Salamon
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Ólafur Guðmundsson
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Suzanne Woolf
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Pekka Savola
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Rob Austein
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Suzanne Woolf
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Mark Andrews
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Jakob Schlyter
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Jaap Akkerhuis
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… J-F C. (Jefsey) Morfin
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Peter Koch
- [dnsop] Re: WGLC on draft-ietf-dnsop-bad-dns-res-… Stephane Bortzmeyer
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Kevin Darcy
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… JINMEI Tatuya / 神明達哉
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Peter Koch
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Olaf M. Kolkman
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… Ted Lindgreen
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… David Meyer
- Re: [dnsop] WGLC on draft-ietf-dnsop-bad-dns-res-… JINMEI Tatuya / 神明達哉