[Dnssec-trigger] Resolution on resume from hibernate (MacOS 10.8)
wouter at nlnetlabs.nl
Tue Apr 9 13:22:51 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
I have created a snapshot of the devel version of dnssec-trigger.
The changes are mostly for OSX, so there is this dmg.
You can install it over your current 0.11. It includes newer ldns and
unbound versions as well as some OSX specific improvements in
- - install on Mountain Lion
- - phil's search domain patch for OSX.
- - hibernation fix for OSX
The hibernation fix is that it detects the system wakeup and at that
time flushes some unbound caches (the infra cache, the requestlist and
it flushes bogus information out of the DNS cache). This should
hopefully make things work.
If you have this, does that still need a kill of mDNSResponder?
If adventurous users feel like it, go on and try out this version, it
should hopefully remove OSX irritations.
On 03/24/2013 12:13 AM, Phil Pennock wrote:
> Seen this twice, don't know enough about Mac internals to track it
> down, but now that it's recurred, I can perhaps prod further in
> MacOS 10.8.3 on a laptop.
> When I resume from sleep/hibernate, sometimes I am now missing
> functioning DNS resolution. At least this time, Chrome was
> running still, so the resume resulted in a Gmail tab failing to
> talk to the server. This *might* affect open communication paths
> to the system resolver?
> I have functioning network, I can ping something outside
> (22.214.171.124), "sudo unbound-control forward" shows the forwarding is
> there, pointing to the local router gateway (which in turn runs
> unbound). Turning off WiFi and turning it back on, does not fix
> it. "sudo unbound-control reload" (and then restoring the forward)
> does not fix it. "Fix" is defined as "ping www.google.com" in a
> Terminal is able to resolve the hostname.
> Only fix is:
> sudo killall -v mDNSResponder
> At which point, everything gets back DNS resolution ability.
> This problem started with dnssec-trigger being installed.
> Anyone have ideas about what might be going on? Failing that,
> suggestions for things to look at, the next time, to better
> DNSSec-Trigger installed: % pkgutil --pkgs | fgrep -i dnssec
> An extract from system.log is attached, including some
> dnssec-trigger failures. I suspect that this is a clue:
> ----------------------------8< cut here
> >8------------------------------ Mar 23 18:39:18 ilmenite
> com.apple.launchd (nl.nlnetlabs.dnssec-trigger-hook): Throttling
> respawn: Will start in 1 seconds ----------------------------8< cut
> here >8------------------------------
> Thanks, -Phil
> _______________________________________________ dnssec-trigger
> mailing list dnssec-trigger at NLnetLabs.nl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the dnssec-trigger