I'm having similar problems with unbound lately. I don't know how long unbound was running, but it has only processed 51031 before I restarted it. There has been no network interruption as far as I can tell. However, what is very strange is this behaviour:
[guus@host]~>host another.host.example.org
[guus@host]~>host -t any another.host.example.org
another.host.example.org has address 192.0.43.10
another.host.example.org has IPv6 address 2001:500:88:200::10
[guus@host]~>host another.host.example.org
[guus@host]~>sudo invoke-rc.d unbound restart
[ ok ] Restarting recursive DNS server: unbound.
[guus@host]~>host another.host.example.org
another.host.example.org has address 192.0.43.10
another.host.example.org has IPv6 address 2001:500:88:200::10
That's host from the bind9-host package. When unbound is behaving strangely,
normal lookups fail, but if I specify -t any I do get proper results. After
restarting unbound things behave normally again.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
