Re: Just in case you want to know: resolv problems

> You haver to distinguish DNS Server cache and DNS client cache.

Oh ok, I didn't got it, sorry.

> Even while chaning resolv.conf to drop out a DNS Server from your  
> query queue, it might be that your CLIENT cache still resolve to  
> whatever it resolved before. This means your client (kannel in this  
> example) will not query the net for the IP it already resolved a  
> while ago.

That's the reason I think may be considered interesting for kannel users.

> Its implementation specific but whatever library you use  to resolve 
> DNS might do that. I dont think thats something kannel  does by itself 
> but the resolver library it uses which is provided by  the operating 
> system. Killing and restarting kannel then makes this  cache being 
> lost, resulting in another query next time at what point  the 
> resolv.conf is queried again.
>
Infact it's what is happening - I think it's the smsbox doing so - I 
should check if it's in the code or not.

> At least this is the behaviour I have seen with other apps in the  
> past on various unix systems.
>
Never happened to me before, I could also be a library decided rule 
infact making a sort of cache from same PID queries to best effort.

>
> Andreas Fink
> Fink Consulting GmbH

Thanks for the ideas, maybe you are right.
J