[Dnssec-trigger] Resolution on resume from hibernate (MacOS 10.8)

[W.C.A. Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Phil,

On 04/10/2013 07:47 PM, Phil Pennock wrote:
> On 2013-04-10 at 09:18 +0200, W.C.A. Wijngaards wrote:
>> Is this VPN related?  There is something wrong when VPNs are
>> used?  I think it gets confused about nameservers, or VPN and
>> dnssec-trigger software conflict about updating nameserver
>> settings.
> 
> No, they're in an office, Juniper router (I think), issuing Google 
> Public DNS as resolvers.

So, the router could be weird (depending on the software on it),
google DNS supports DNSSEC.  So I think the issue is mostly the
configuration of the OSX machine.  I was wondering if there was other
software on that OSX machine, such as VPN software, that messes with
the nameserver configuration; and in combination with dnssec-trigger's
messing with the nameserver configuration this leads to a failure to
resolve?

Best regards,
   Wouter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRZl9ZAAoJEJ9vHC1+BF+NBNMP/R0IKf/MHeUlNTolCxW7QWTx
2dkdoEGd2N9GnS/4hJtBREF8lrz+YZjmghd+mUpZqiRP8epFdbjgA0LZ7ATsDj86
foWQBG1VL9TFARpq4y5jKndTOlPgU4kVKMdwqx9Qcaw5yClp8fE8Zin2lTa2SeEM
H1HJ8PquQWfYnv9otJuAl2wml+2KNEOqqc5DPL+OHjIINoK6hugB2VLG0qxX6iIL
XNu2CdS4R4iAjRholUyr+UZ3E22zJijNC6VfjljdGta+3vBNoObL9bBcm8R/zQNT
M80Jf+pSl/R4urUhHLpIXpdc6gBDiKOr9mEiDo3offZ6yeKHkCgYdRS5U1eBkTSE
LyOlrnBDDzIwOADszMUl3EWN/Lwd2lvz7mge3EHqgjaoZgKa56TrGx10ZaarhVHQ
xTFrtXbZdrRddCVM/JzL2DsyNQnUDidslcSRTzNvJCpV9aadNtA1XlHK3dCfefPy
9uJjPsIJmXGMDkntee5nu4dN34lBbJA8oEh9HnoiHcttO6tGG+4syacdpxRB9BcH
4qsg9NyaT2cY6EMAt1N638+ur1YMokqVqrvQrCXpihTCSnPyh+7RV8affGlZ5E0F
qC+1P8bVMfaGm3kZ3Mdqq5LvZ24Rrv90KX0Qo0Q1GGkhdw7ZLCwJ4eXhX1CGe2fY
0oulQRzi40bCmh1fA2ux
=HGta
-----END PGP SIGNATURE-----