can't resolve

A. Schulze sca at
Fri Nov 30 12:57:28 UTC 2018


we notices the name "" is un-resolvable via one of our  
unbound instances.
while looking for reasons we found no problem on a standby system.
unbound-1.8.1 configuration is *identical* (except listen ip)
The issue is reproducible even after restarting both instances.

neither nor
show (me) an obvious reason.

Some random tries later I configured "domain-insecure:"  
which solved the problem.

Cold someone explain that behaviour? Maybe we could learn again some  
more experiences debugging strategies ...


More information about the Unbound-users mailing list