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: [email protected]
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
_______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
