Re: resolver doesn't see resolv.conf changes

2006-04-09 Thread Ulrich Spoerlein
Dmitry Pryanishnikov wrote: > Hello! > > On Sat, 8 Apr 2006, Ulrich Spoerlein wrote: > >Good idea, but this defeates the hierarchical purpose of DNS. Now my > >caching DNS is always querying the root DNS servers. > > Sorry, but what kind of hierarchy does it defeat? If client's query > can't be

Re: resolver doesn't see resolv.conf changes

2006-04-09 Thread Hajimu UMEMOTO
Hi, > On Sun, 9 Apr 2006 18:06:31 +0200 > Ulrich Spoerlein <[EMAIL PROTECTED]> said: spoerlein> Very nice. I wonder though, why has resinit to come before files? spoerlein> Shouldn't it be files resinit dns? Yup, it is enough to put resinit just before dns, and it should work. However, o

Re: resolver doesn't see resolv.conf changes

2006-04-09 Thread Ulrich Spoerlein
Lowell Gilbert wrote: > Lowell Gilbert <[EMAIL PROTECTED]> writes: > > Ulrich Spoerlein <[EMAIL PROTECTED]> writes: > > > Lyndon Nerenberg wrote: > > > > The solution is to run a local caching nameserver instance. You should > > > > do this anyway, for > > > > performance reasons. Add 'named_ena

Re: resolver doesn't see resolv.conf changes

2006-04-09 Thread Ulrich Spoerlein
Hajimu UMEMOTO wrote: > Hi, > Oops, it should be: > > http://www.imasy.or.jp/~ume/FreeBSD/nss_resinit-20060408.tar.gz Very nice. I wonder though, why has resinit to come before files? Shouldn't it be files resinit dns? Anyway, after some limited testing, it seems to work fine. Thanks a bun

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Lyndon Nerenberg
On Apr 8, 2006, at 1:39 AM, Ulrich Spoerlein wrote: Good idea, but this defeates the hierarchical purpose of DNS. Now my caching DNS is always querying the root DNS servers. That's how the DNS works. You query the root once for the TLD, then cache the NS records for the TLD's servers, poin

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Dmitry Morozovsky
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

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Dmitry Pryanishnikov
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

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Dmitry Morozovsky
On Sat, 8 Apr 2006, Dmitry Pryanishnikov 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

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Dmitry Pryanishnikov
Hello! On Sat, 8 Apr 2006, Ulrich Spoerlein wrote: Good idea, but this defeates the hierarchical purpose of DNS. Now my caching DNS is always querying the root DNS servers. Sorry, but what kind of hierarchy does it defeat? If client's query can't be satisfied from provider's DNS cache, and d

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Chuck Swiger
Ulrich Spoerlein wrote: Lyndon Nerenberg wrote: The solution is to run a local caching nameserver instance. You should do this anyway, for performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, and modify your /etc/dhclient.conf as follows: Good idea, but this defeates the hierarchic

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Lowell Gilbert
Lowell Gilbert <[EMAIL PROTECTED]> writes: > Ulrich Spoerlein <[EMAIL PROTECTED]> writes: > > > Lyndon Nerenberg wrote: > > > The solution is to run a local caching nameserver instance. You should > > > do this anyway, for > > > performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, an

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Lowell Gilbert
Ulrich Spoerlein <[EMAIL PROTECTED]> writes: > Lyndon Nerenberg wrote: > > The solution is to run a local caching nameserver instance. You should do > > this anyway, for > > performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, and modify > > your > > /etc/dhclient.conf as follows: >

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Ulrich Spoerlein
Lyndon Nerenberg wrote: > The solution is to run a local caching nameserver instance. You should do > this anyway, for > performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, and modify > your > /etc/dhclient.conf as follows: Good idea, but this defeates the hierarchical purpose of D

Re: resolver doesn't see resolv.conf changes

2006-04-08 Thread Ulrich Spoerlein
Hajimu UMEMOTO wrote: > [resinit patch] > > It seems working on my 7-CURRENT box and 6-STABLE box. However, it > should be tested more. Thanks! I'll give it a try. Though it takes me a while to roam around, I'll report back! Ulrich Spoerlein -- PGP Key ID: 20FEE9DD E

Re: resolver doesn't see resolv.conf changes

2006-04-07 Thread Rostislav Krasny
> when switching my laptop from LAN to a dialup connection, applications > started _before_ the switch will still try to send DNS queries to my > local DNS server. This isn't ideal, and the only workaround I've found > so far is to restart the application. > > Is the resolver supposed to periodica

Re: resolver doesn't see resolv.conf changes

2006-04-07 Thread Artyom Viklenko
> Hi, > >> On Wed, 5 Apr 2006 17:27:19 +0200 >> Ulrich Spoerlein <[EMAIL PROTECTED]> said: > > spoerlein> Is the resolver supposed to periodically check for updates to > the > spoerlein> resolv.conf, or are the applications somehow caching the IP of > the DNS > spoerlein> server? > > Trad

Re: resolver doesn't see resolv.conf changes

2006-04-07 Thread Hajimu UMEMOTO
Hi, > On Fri, 7 Apr 2006 12:15:54 -0400 > "Rong-En Fan" <[EMAIL PROTECTED]> said: grafan> The file is not there. I got 404. Oops, it should be: http://www.imasy.or.jp/~ume/FreeBSD/nss_resinit-20060408.tar.gz Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama,

Re: resolver doesn't see resolv.conf changes

2006-04-07 Thread Hajimu UMEMOTO
Hi, > On Wed, 5 Apr 2006 17:27:19 +0200 > Ulrich Spoerlein <[EMAIL PROTECTED]> said: spoerlein> Is the resolver supposed to periodically check for updates to the spoerlein> resolv.conf, or are the applications somehow caching the IP of the DNS spoerlein> server? Traditionally, the resol

Re: resolver doesn't see resolv.conf changes

2006-04-06 Thread Lyndon Nerenberg
Is the resolver supposed to periodically check for updates to the resolv.conf, or are the applications somehow caching the IP of the DNS server? No, resolv.conf is only read once when the resolver routines initialize. The solution is to run a local caching nameserver instance. You should do t