Home made resolver - why ?

[David TAILLANDIER]

>> /var/argus/log contains tons of:
>> --> RESOLV recv failed: refused connection
> 
> this is normal, it is not an error.
> it means the nameserver was down.
> argus will then try the next one.

I don't know if Argus try the next one. But Argus don't resolve anything 
if the first server refuse to server any dns query.




>> The real problem with that is: don't using standard feature often lead 
>> to problems.
>> Someone else already wrote a good resolver and Perl have access to it.
> 
> 
> yes, "someone" wrote a good resolver, and "someone" included in the 
> argus distribution.

Okay :-)
You can think this is a good resolver. But the facts are against that: 
it broke on the first not-ideal case I saw.






> the "hack" is to remove the "Resolv" line that you put in your config file.

We then lose the ability to handle "moving" addresses. If I understand 
the documentation: the dns names are resolved when the daemon start, and 
never after that.

If I move my.server.com to another location, I have to restart Argus 
daemon. Worst, if I have my.site.com on a dynamic ip, Argus have no way 
to re-resolv it. Even worst, if I want to ping computers configured with 
DHCP and dynamic dns I'm stuck too. Or I have to restart Argus with cron 
every 5 minutes, which is not an option for most admin.