Directory-based client configuration (was: "Dynamic" dhcp-client configuration using two interfaces? )

[Michael Richardson]

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Kenneth" == Kenneth Porter <shiva at sewingwitch.com> writes:
    >> Daniel, you likely should run a local named, and force the
    >> /etc/resolv.conf to be 127.0.0.1. Applications which read
    >> /etc/resolv.conf won't read it again if it changes, while named will
    >> pay attention to what interfaces are up, and use them. You can also
    >> edit /etc/named.conf's forwarder's entry if you really want, and "rndc
    >> reload" it much easier.
    >> 
    >> The default route will otherwise be handled by dhclient.

    Kenneth> I was bringing up a Fedora system this week and wanted to set it
    Kenneth> up for DHCP but with a caching nameserver. A bit of digging
    Kenneth> around revealed the PEERDNS=no mechanism to suppress rewriting
    Kenneth> of resolv.conf.

    Kenneth> It struck me that a more general solution would be to do
    Kenneth> something like other directory-based configurations, and have
    Kenneth> dhclient-script iterate through a set of scripts in a config
    Kenneth> directory of its own. The scripts would be supplied by other

  Yes, I would generally agree.
  I think it needs to be a bit more complicated, but your system could work.

  For the mechanism to work right, someone needs to spend some time to do
integration work, and get buy in from multiple system application writers,
not just the people doing a particular distro.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr at xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBP9DBIoqHRg3pndX9AQE8TgQAswGdtKDANE4dobnc6KAWz3Axsgj+Cia6
Nu2+d0Dv9QSln/NtzezwL1R4WIel2QWAAi0V+DB4Iwd72xHMQr96RZKtmhbNyfBp
/2bIsw8Hxz2rptL20tSgMeWL2QYugO7szJ8yCw+IIUJy2A6zo48cQtc8u+8XP+fb
xAtCIGFSsHI=
=4FCN
-----END PGP SIGNATURE-----