Date: Sat, 8 Apr 2006 23:00:27 +0300 (EEST) From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: Dmitry Morozovsky <marck@rinet.ru> Cc: stable@freebsd.org, Lyndon Nerenberg <lyndon@orthanc.ca>, Ulrich Spoerlein <spoerlein@googlemail.com> Subject: Re: resolver doesn't see resolv.conf changes Message-ID: <20060408220204.P64496@atlantis.atlantis.dp.ua> In-Reply-To: <20060408223657.D67402@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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! On Sat, 8 Apr 2006, Dmitry Morozovsky wrote: > DP> Sorry, but what kind of hierarchy does it defeat? If client's query > DP> can't be satisfied from provider's DNS cache, and doesn't refer to > DP> domain which is hosted on ISP, then provider's DNS server will make > DP> first query to root DNS server, and then will walk down domain hierarchy > DP> (e.g. .ua -> .dp.ua -> atlantis.dp.ua). So setting client's DNS to directly > DP> query root servers defeats just the provider's DNS cache. > > Not in other ways delegated domains, i.e. XXX.local. I think that we're talking about official domain hierarchy here, aren't we? And those XXX.local and YYY.homenet domains are outside this hierarchy. And, BTW, ISP clients are rarely interested in internal ISP's .local domains. They're interested in ISP servers (SMTP, POP3/IMAP, NNTP, WEB), and these servers usually have official names in public ISP domains, accessible via official hierarchy (down from root servers). Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060408220204.P64496>