On 4-May-04, at 1:50 PM, Steven M. Bellovin wrote:

> Not easily, for several reasons.  First, the machine moves around, and
> from inside the corporate firewall I can't get to outside nameservers
> directly.  Second, web browsers seem to read resolv.conf once, at
> startup, which means it needs to be stable; 127.0.0.1 does the trick.
> (I have a bizarre script in /etc/dhclient-enter-hooks that replaces
> make_resolv_conf() with something that builds a named.conf file and
> then restarts named (and ntpd).  That usually works, though I sometimes
> encounter weird !@#$%^ hotel boxes that really want me to use a
> resolv.conf file instead.
>
I see. Yeah, you're right.  I don't see a non-duct-tape answer here.