Re: [CFR] reflect resolv.conf update to running application

From: Brooks Davis (brooks_at_one-eyed-alien.net)
Date: 09/21/05

  • Next message: Ron Nelson: "school mascot items" 
    Date: Wed, 21 Sep 2005 07:09:43 -0700
To: "Matthew N. Dodd" <mdodd@FreeBSD.ORG>

    On Thu, Sep 15, 2005 at 09:59:48AM -0400, Matthew N. Dodd wrote:
    > On Thu, 15 Sep 2005, Doug Barton wrote:
    > >Yes, include works, but it runs a similar risk to modifying the
    > >named.conf file, namely if the syntax of the the statements in the
    > >include file are not right, loading named.conf will fail. So, we should
    > >build some caution into the process of updating the file, but that's
    > >easily done with the named-checkconf program that comes with the
    > >distribution.
    >
    > I'm not sure such paranoia is needed; dhclient has always exposed the
    > system to the risk of having an invalid resolv.conf and regenerating the
    > named.conf file is no different. Since we're regenerating the included
    > file completely I don't see that this is risky at all.

    The domain name server values will be valid host names. dhclient checks
    that so we can count on it. I had broken the search checks, but have
    since fixed that. It might be useful to still write a resolv.conf that
    only refers to 127.0.0.1 and includes the search directive if we write
    the forwarder's file.

    -- Brooks 

    --
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

  • Next message: Ron Nelson: "school mascot items"