[Dnssec-trigger] OS X, resolv.conf
wouter at NLnetLabs.nl
Tue Jan 3 15:04:09 UTC 2012
-----BEGIN PGP SIGNED MESSAGE-----
On 01/03/2012 03:36 PM, Phil Regnauld wrote:
> W.C.A. Wijngaards (wouter) writes:
>> with eg:
>> sudo vi /etc/dnssec-trigger/dnssec-trigger.conf
>> or use another editor that you like.
>> And change xyz.fr or put a commentsign (#) at the start of that line.
>> The config file is documented, so it should be (relatively) obvious.
> Right, I've played around with it, and commented out the domain: and
> search: parameters.
> Now, dns settings show "nothing.invalid" as the search suffix.
> I see the comment:
> # the search path from DHCP is not picked up, it could be used to misdirect.
> Is there a way to override this behaviour ? That's a policy decision.
There is no way to override this behaviour (at this time), and it would
be somewhat difficult to make portable.
If you need a couple you use you can put the search path into the config
file manually, at this time. This is why I pick it up on install, e.g.
if you install at home/work you get the 'right' DHCP searchpath all the
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the dnssec-trigger