DNS resolution fails after resolv.conf update

[Stanislav Baiduzhyi]

On Monday 04 May 2015 22:26:26 Bernd Eckenfels wrote:
> not sure how I feel about the res_init(). Depending on the backends
> used this might be expensive. Especially since it wont be rate
> limited. The negative-ttl of 10s is for single records I thing. So at a
> minimum you should rate-limit res_init to the same negative-ttl time).
> 
> But another aspect: this is also a problem for positive answers. Only
> because you get an answer does not mean it is the NS you wanted to
> query. Maybe a background refreshing could solve both? Would also
> reduce concurrency.
> 
> debian/ubuntu BTW seems to have a rather elaborate reload hook
> mechanism:
> http://manpages.ubuntu.com/manpages/gutsy/man8/resolvconf.8.html
> 
> 
> But that is I guess hard to integrate with JVM.

Bernd,

I like the idea with background thread. I'll dig into it to see what other 
threads are there, maybe there is already something similar that can extend 
its purpose. or will try to create additional thread for that.

-- 
Regards,
    Stas