Maintained by: NLnet Labs

Unbound not always resolving immediately after start.

Frank de Bot
Fri Sep 11 11:39:21 CEST 2015


Hi,

Under FreeBSD I'm setting up a resolv-only unbound server. While testing
I've noticed some domain do not resolve (server returns SERVFAIL)

When running verbosily I noticed this in the log:

[1441963936] unbound[22814:0] info: processQueryTargets: ns.tweakdns.nl.
AAAA IN
[1441963936] unbound[22814:0] debug: request ns.tweakdns.nl. has
exceeded the maximum number of glue fetches 37
[1441963936] unbound[22814:0] debug: request ns.tweakdns.nl. has
exceeded the maximum number of glue fetches 37
[1441963936] unbound[22814:0] debug: return error response SERVFAIL
[1441963936] unbound[22814:0] debug: validator[module 0] operate:
extstate:module_state_initial event:module_event_moddone
[1441963936] unbound[22814:0] info: validator operate: query
ns.tweakdns.nl. AAAA IN
[1441963936] unbound[22814:0] debug: iterator[module 1] operate:
extstate:module_wait_subquery event:module_event_pass
[1441963936] unbound[22814:0] info: iterator operate: query
tweakers.net. A IN
[1441963936] unbound[22814:0] info: processQueryTargets: tweakers.net. A IN
[1441963936] unbound[22814:0] debug: out of query targets -- returning
SERVFAIL
[1441963936] unbound[22814:0] debug: return error response SERVFAIL

A second query about 15/20 second later does work and it's cached.

A lot of domain  resolve from the start without any trouble. I don't
know where exactly to look for the problem. Is this a problem that could
reside in Unbound?


Regards,

Frank de Bot