Maintained by: NLnet Labs

[Unbound-users] order of forward-addr

martin f krafft
Mon Feb 8 00:56:59 CET 2010


The behaviour of unbound suggests that forward-addr resolvers are
used as a pool for a given zone, i.e. they are tried in random
order. Is there a way to fix the order?

The reason is that I don't want to hardcode the resolver list on my
laptop and thus have resolvconf auto-generate it to include the
sixxs.net dnscache[0]. As the underlying Ethernet connection
probably got told about some DNS IPs via DHCP as well, those end up
in the list as well. Since the sixxs.net dnscache returns augmented
values for some domains (e.g. Google IPv6), the behaviour of unbound
is now unpredictable.

0. http://www.sixxs.net/tools/dnscache/

Any idea what I can/should do?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
love your enemies; they'll go crazy
trying to figure out what you're up to.
 
spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
URL: <http://unbound.nlnetlabs.nl/pipermail/unbound-users/attachments/20100208/62ab6fe1/attachment.pgp>