On Tue, 6 Jan 2004, "Greg A. Woods" <woods@weird.com> wrote:
> Another alternative would be to re-initialize it only if an error is
> returned by a lower-level routine.

I was going to offer that suggestion, but realized that errors aren't the
only reason to re-read resolv.conf.  

Move a machine from one network to another, and if it can reach the
Internet from both places, it will of course be able to use any (or, at
any rate many) DNS on the Internet.  But it won't pick up names that
aren't exposed to the Internet, making it blind to its internal network.  

One could say, OK, so tie it to a dhcp update, but that's no good, either,
because there's no rule that says both (or either) of the networks are
dhcp-managed.  

I don't know how this very interesting discussion will shake out, but the
problem clearly calls for an on-demand -- or at least periodic -- refresh.
 

--jkl