Re: Update of RFC 2606 based on the recent ICANN changes ?

Bill Manning <bmanning@ISI.EDU> Mon, 07 July 2008 22:50 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39AC23A6B55; Mon, 7 Jul 2008 15:50:14 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFFE03A6B51 for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 15:50:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.026
X-Spam-Level:
X-Spam-Status: No, score=-1.026 tagged_above=-999 required=5 tests=[AWL=0.373, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_74=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-cVMDp1dUjt for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 15:50:11 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id CDDB93A6B3D for <ietf@ietf.org>; Mon, 7 Jul 2008 15:50:11 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m67Mnrbo028767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 7 Jul 2008 15:49:54 -0700 (PDT)
Received: (from bmanning@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id m67Mnrgi028766; Mon, 7 Jul 2008 15:49:53 -0700 (PDT)
Date: Mon, 7 Jul 2008 15:49:53 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Ted Faber <faber@ISI.EDU>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Message-ID: <20080707224953.GA18872@boreas.isi.edu>
References: <20080707133210.AWH55905@m1.imap-partners.net> <20080707203828.GC2300@zod.isi.edu> <20080707204428.GD2300@zod.isi.edu> <20080707210431.GA17533@boreas.isi.edu> <20080707212531.GC2222@zod.isi.edu>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20080707212531.GC2222@zod.isi.edu>
User-Agent: Mutt/1.4.2.2i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
Cc: ietf@ietf.org, moore@network-heretics.com, Bill Manning <bmanning@ISI.EDU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Mon, Jul 07, 2008 at 02:25:31PM -0700, Ted Faber wrote:
> On Mon, Jul 07, 2008 at 02:04:31PM -0700, Bill Manning wrote:
> > On Mon, Jul 07, 2008 at 01:44:28PM -0700, Ted Faber wrote:
> > > On Mon, Jul 07, 2008 at 01:38:28PM -0700, Ted Faber wrote:
> > > > On Mon, Jul 07, 2008 at 01:32:10PM -0700, moore@network-heretics.com wrote:
> > also...  
> > % dig version.bind txt chaos @128.9.160.161
> > ;; ANSWER SECTION:
> > version.bind.           0S CHAOS TXT    "9.4.2"
> > 
> > 	so - recent resolver code does this trick.
> 
> Fair enough.  Perils of working for ISI, I suppose - modern
> infrastructure.
> 
> Not to argue with someone who's forgotten more about DNS than I know,
> but I was able to get it to work from zig.usc.edu as well. On zig (a
> Linux box talking to an ambiguously identified "USC Bind 9x" server)
> ping needed the trailing dot on hk. to work.  And by "got it to work, I
> mean "typed ping".  I also had no trouble on a FreeBSD machine talking
> to bind 9.3.3.  It works at home, too, but that's also a 9.4.2 bind.
> 
> -- 
> Ted Faber
> http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
> Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG

	so... the point i was tryig to make was/is:

	simple queries only help if you know:
		) the version of software running on your caching server
		and
		) the search list defined by your "resolv.conf" 

	zig.usc.edu,
	boreas.isi.edu,
	luna-base.org,
	ep.net,
	lcs.mit.edu,
	comcast.net,

	all run slightly different caching code and variable search lists.

	you, me, Ted, Keith, John, et.al.  are going to see -slightly- different
	responses  when presenting our individual local caching servers with
	non-terminated DNS strings.

	Japp and Karl both hinted at this problem - local policy  is the worst policy,
	except for all the others.  Your local DNS admin can (and occasionally they do)
	toss you into a random walled-DNS garden that has only a passing similarity to
	what you think of as the "Internet".   http://www.icann.org/committees/security/sac032.pdf
	is illustrative.  

-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf