From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 20:10:47 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A4D916A402 for ; Sat, 8 Apr 2006 20:10:47 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DF0743D48 for ; Sat, 8 Apr 2006 20:10:46 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k38KAhX4082649; Sun, 9 Apr 2006 00:10:43 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sun, 9 Apr 2006 00:10:43 +0400 (MSD) From: Dmitry Morozovsky To: Dmitry Pryanishnikov In-Reply-To: <20060408220204.P64496@atlantis.atlantis.dp.ua> Message-ID: <20060409000727.E67402@woozle.rinet.ru> References: <20060405152718.GA1003@roadrunner.q.local> <20060406153938.C78654@orthanc.ca> <20060408083955.GA1041@roadrunner.q.local> <20060408211725.H47923@atlantis.atlantis.dp.ua> <20060408223657.D67402@woozle.rinet.ru> <20060408220204.P64496@atlantis.atlantis.dp.ua> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sun, 09 Apr 2006 00:10:44 +0400 (MSD) Cc: stable@freebsd.org, Lyndon Nerenberg , Ulrich Spoerlein Subject: Re: resolver doesn't see resolv.conf changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 20:10:47 -0000 On Sat, 8 Apr 2006, Dmitry Pryanishnikov wrote: DP> > DP> Sorry, but what kind of hierarchy does it defeat? If client's query DP> > DP> can't be satisfied from provider's DNS cache, and doesn't refer to DP> > DP> domain which is hosted on ISP, then provider's DNS server will make DP> > DP> first query to root DNS server, and then will walk down domain DP> > hierarchy DP> > DP> (e.g. .ua -> .dp.ua -> atlantis.dp.ua). So setting client's DNS to DP> > directly DP> > DP> query root servers defeats just the provider's DNS cache. DP> > DP> > Not in other ways delegated domains, i.e. XXX.local. DP> DP> I think that we're talking about official domain hierarchy here, aren't we? DP> And those XXX.local and YYY.homenet domains are outside this hierarchy. And, DP> BTW, ISP clients are rarely interested in internal ISP's .local domains. DP> They're interested in ISP servers (SMTP, POP3/IMAP, NNTP, WEB), and these DP> servers usually have official names in public ISP domains, accessible via DP> official hierarchy (down from root servers). Situations vary. There may be patterns where one laptop should be involved in corporate networks with .local (and somewhat restricted or even faschist-style outgoing firewalls; I *do* know some organizations where you can't even ssh out without organizational problems) and some possibly totally different public networks. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------