Re: spoke too soon...

["Stephen Biggs" <s_c_biggs@xxxxxxxxxxx>]

Ahhh....

Here, I thought my Linux configuration was messed up...

... and there's no way to turn it off, but there should be... if I am 
running a server, I should have the ability to turn off this security if I 
don't need it.

On 4 Oct 2001, at 11:34, Eugene L. Vorokov wrote:

> > Sorry... I am a real newbie at this... it is, in fact, a resolv problem.  
> > With -x 10 I see the repeated callx to get_res returning with 0 (-
> > 1,0)... this accounts for the timeout.
> > 
> > The weird thing here is that my /etc/resolv.conf has one line in it that 
> > says "order hosts" and my /etc/hosts defines both the single client 
> > and the server according to IP, so this should return with a name 
> > and not timeout... 
> 
> Forget about /etc/hosts. ircd does NOT use traditional resolver, because
> lookups with gethostbyname() and such are blocking. This way ircd would
> stop all it's operations while trying to lookup a single host which
> does not exist.
> 
> ircd uses /etc/resolv.conf in it's own way. It only recognizes "nameserver"
> and "search" keywords there, and uses them to retrieve information of what
> nameserver to use. Once it has nameserver IP address, it does all DNS
> stuff by itself, with non-blocking policy. It does that with no regards
> to how your standard resolver is configured.
> 
> This is why you do need a working *nameserver*, not other kludges like
> /etc/hosts, to have conveniently working ircd.
> 
> Regards,
> Eugene
>