inconsistent forward-zone behavior between config files, unbound-control
wouter at nlnetlabs.nl
Wed Sep 23 09:47:31 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 09/22/2015 07:02 PM, Mike Brown via Unbound-users wrote:
> It is quite possible I am just clueless and doing things all wrong,
> so please forgive me if this is a waste of your time. I've Googled
> and experimented for hours, and am no closer to understanding
> what's going wrong here.
Not a clue about comcast or uribl, but your unbound.conf looks weird:
> # cat /var/unbound/conf.d/uribl.conf forward-zone: name:
> multi.uribl.com forward-host: multi.uribl.com
This entry creates a loop, where unbound has to lookup multi.uribl.com
to lookup multi.uribl.com, and to do that it has to lookup
multi.uribl.com ... And that causes it to fail.
Also multi.uribl.com is a website, and unbound wants nameservers (the
right hand side of the dig multi.uribl.com NS lookup).
To remove the endless loop you can type IP adresses (with
forward-addr: ip), but in this case, uribl has nameservers that do not
cause a loop:
Another point, it should be a stub-zone, because those are
authoritative servers that you are listing in the config. Use
stub-zone: and stub-host: in the uribl.conf file.
Best regards, Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
More information about the Unbound-users