[Unbound-users] Unbound stops answering after ADSL-line bounce
PaulTaylor at winn-dixie.com
Fri Feb 10 15:50:27 UTC 2012
Thank you - I'll file these commands away for future reference.
Previously, I tried recreating the problem a few times, but after
waiting 15 minutes (per your previous advice) after the WAN recovery,
DNS has worked. I've not tried leaving my internet connection down for
much more than about 10 minutes, though.
From: W.C.A. Wijngaards [mailto:wouter at nlnetlabs.nl]
Sent: Friday, February 10, 2012 9:34 AM
To: Paul Taylor
Cc: unbound-users at unbound.net
Subject: Re: [Unbound-users] Unbound stops answering after ADSL-line
-----BEGIN PGP SIGNED MESSAGE-----
On 02/10/2012 02:28 PM, Paul Taylor wrote:
> On the original topic of this thread, I have another incident to
> After experiencing some strangeness with my NAS (where unbound was
> running previously), I moved Unbound to an installation of pfSense
> running on an old net4801. I believe pfSense is still on version
> of Unbound. I configured it pretty much identically to my NAS
> installation of Unbound. By that, I mean that I have numerous
> forwarders added for various CDNs, with a "." forwarder pointing to
> OpenDNS. DNSSEC validation is disabled. About two weeks had passed
> with no further problems, until this morning.
> Just before I was about to leave home for work (just after 7 AM), my
> daughter told me that the internet was down. I checked my router and
> saw that the internet connection went down last night for a little
> an hour.. It recovered about 3:15 AM. So, it had been up and
> operational for almost 4 hours by the time I started looking at the
> issue. A quick nslookup showed SERVFAIL replies. Since I had to
> for work, I didn't have time to do much in the way of troubleshooting.
> I recycled the service via pfSense's Services page (I think it just
> kills and restarts the service), and DNS was resolving properly again.
It should not be down for that long; 15 minutes really.
> Unfortunately, since it's on an embedded box, I didn't have logging
> enabled, and I don't know what commands, if any, I could run that let
> you see the "state" Unbound is stuck in when this happens.
unbound-control verbosity 4 ; then nslookup and capture the logs (which
are then plentiful).
unbound-control dump_infra > tofile.txt
that shows the state of the infrastructure cache.
-----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 Unbound-users