Date: Mon, 14 Apr 2008 13:26:14 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: "Eygene Ryabinkin" <rea-fbsd@codelabs.ru> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-current@freebsd.org Subject: Re: [RFC] Automated generation of /etc/resolv.conf from the rc.d script Message-ID: <5f67a8c40804141026s27672065sb11a7f327572c0f2@mail.gmail.com> In-Reply-To: <dEZnki0Fi32EvMrDEnqcgDeNQSc@Bbw9J2Iynx0QjNoWuQ4YSitYS3A> References: <7ExUpek150AdEdP4WR1b6w@lz%2BEvuNSgXKgs9kqjMxQNA> <72123.1197626129@critter.freebsd.dk> <dEZnki0Fi32EvMrDEnqcgDeNQSc@Bbw9J2Iynx0QjNoWuQ4YSitYS3A>
index | next in thread | previous in thread | raw e-mail
On Fri, Dec 14, 2007 at 6:14 AM, Eygene Ryabinkin <rea-fbsd@codelabs.ru> wrote: > This can be achieved with the script /etc/dhclient-exit-hooks that > will create the file with named 'forwarders' clause using values > from 'new_domain_name' and 'new_domain_name_servers' variables that > are exported to the hooks script by /sbin/dhclient-script. The > former file can be included from named.conf, so the restart or > reload of the local named instance from the exit hooks script will > do the trick. Last I tried, the OpenBSD dhclient we imported a year ago blithely ignored the dhclient-exit-hooks scripts. This is annoying because in my application, I want to set specific routes not default routes on a successful DHCP (ie: a tunneling CPE device). I had to revert to the ISC-DHCP to restore working dhclient script functionality. Note also that the source and man documentation on this subject appear to document the correct behaviour (not the behaviour of the system).home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40804141026s27672065sb11a7f327572c0f2>