forward zones with broken forwarders
wouter at nlnetlabs.nl
Tue May 8 08:57:10 UTC 2018
On 08/05/18 10:44, Florian Riehm via Unbound-users wrote:
> Often I see unbound configurations with multiple forwarders for zones
> like this:
> name: "."
> forward-addr: 220.127.116.11
> forward-addr: 18.104.22.168
> forward-addr: 22.214.171.124
> forward-addr: 126.96.36.199
> The intention of customers for such configurations are redundancy purposes.
> As long as all forwarders are reachable the configuration works well and
> provides loadbalancing for the forwarders. But if one forwarder becomes
> unreachable, unbound keeps asking it. Timeouts occur, many requests fail
> dns resolution becomes very slow. This means the redundancy requirement
> is not
> fulfilled. I would expect that the infra cache is able to track if a
> becomes unreachable, but that seems not to be true.
> Is there a way to configure unbound to deal with unreachable forwarders
> in a
> better way?
This question was already asked by someone else, and a fix is in the
code repository. That will mark the forwarders as not working and
select the working forwarders, automatically. After a brief couple of
timeouts to detect the failing addresses (a second, or a couple of
Best regards, Wouter
> Thanks & Regards
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Unbound-users