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

[W.C.A. Wijngaards]

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

Hi Phil,

I have created a snapshot of the devel version of dnssec-trigger.
The changes are mostly for OSX, so there is this dmg.

http://nlnetlabs.nl/~wouter/dnssectrigger-0.12_20130409.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
dnssec-trigger:
- - 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.

Best regards,
   Wouter

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
> future.
> 
> 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
> (8.8.8.8), "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
> diagnose?
> 
> DNSSec-Trigger installed: % pkgutil --pkgs | fgrep -i dnssec 
> nl.nlnetlabsdnssectrigger011ForMacosX10.7.Package_Root.pkg
> 
> 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[1] (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 
> http://open.nlnetlabs.nl/mailman/listinfo/dnssec-trigger
> 

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

iQIcBAEBAgAGBQJRZBYrAAoJEJ9vHC1+BF+NpIMP/jNc3SVEoL/O/DfSKimZFPKK
O0bZXapxXNfjWtmvP8tkeouoH+LpWezaIqBv4jjx1q0Apx0vvic8mb1N+dEEa35K
FrtN3FZ6aoEyvygJvyWtrWqzsb7GXIAJ5889fbhfXO1JLoq6eHKNNmtH3/FoaPaf
2ujopBicjLSSYVbnXr9BbETRH93XMCNBrr1/j2HDUD25GFJiaWFmaJt7ZhNfPqvi
gr4FGLbqLqN5GZF5J3TiuYQMPnERCQtvy3j76BVM7mta43iZ6U5LPE6TtDi47RbJ
rVFquZy9Khr4M+SR1oj6aUNHlf2fizWqQIdsAJnudICJf5pRZn10kW96+h6ib3Zr
97YrLw4egUglgRQyakhupg8Yda8XEcrFiuTx3uKauw78W5IOQ7eT9b7PM1FhD1i/
ubF8ZeepI4GD62lnb/DuauIerRXb5XJ3swuAOkYrKq0kmLttRxkmUN7HbltRE5en
MuM1RHDGG3QJRG736uEPiKwIBf1h6sigu5KuHzzaDV7UZzN1aCNudzVEzMaXAIFj
Fq728yXyUaUCiorgf6J33/ms5DXRXwrfx8EjvgE8Po3DvLjU5/QzSSlkcmDMY5Hk
MhLR4w0p+pLXOJFdy3edfG3gZql+VmYk+cqZzXSLfhtG4KJCIA2EXOl8nBT1Ieit
//biu+gc9+c0lAM4uumV
=L8KX
-----END PGP SIGNATURE-----