The customer is planning to use the JRE DNS resolver instead of the OS resolvers (he uses Solaris 8/10 and Linux Red Hat 2.x/3.x/4.x/5.x). His need is to be able to have the JRE regularly re-read the /etc/resolv.conf file as he updates this file constantly in his LAN.

He also explained me that this is the behavior for Apache 1.3.1 he is using, but Apache is forking processes, hence it re-read the resolv.conf file.