Slightly related - I see that --all-servers might have become the default now?
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2010q2/003942.html
Is there some way to disable this and use "known to be up"? The reason is that
I'm seeing a large ICMP "unreachable" response generated for the slower
response,
plus the additional bandwith, eg tcpdump for a request for www.yahoo.co.uk:
22:23:40.151666 IP 10.141.36.76.25630 > 8.8.4.4.53: 11049+ AAAA?
www.yahoo.co.uk. (33)
22:23:40.151993 IP 10.141.36.76.25630 > 8.8.8.8.53: 11049+ AAAA?
www.yahoo.co.uk. (33)
22:23:40.850776 IP 8.8.4.4.53 > 10.141.36.76.25630: 11049 3/1/0 CNAME
rc.yahoo.com., CNAME rc.g01.yahoodns.net., CNAME any-rc.a01.yahoodns.net. (178)
22:23:41.014108 IP 8.8.8.8.53 > 10.141.36.76.25630: 11049 3/1/0 CNAME
rc.yahoo.com., CNAME rc.g01.yahoodns.net., CNAME any-rc.a01.yahoodns.net. (178)
22:23:41.014217 IP 10.141.36.76 > 8.8.8.8: ICMP 10.141.36.76 udp port 25630
unreachable, length 214
22:23:41.401743 IP 10.141.36.76.10248 > 8.8.4.4.53: 25285+ A? www.yahoo.co.uk.
(33)
22:23:41.764124 IP 8.8.4.4.53 > 10.141.36.76.10248: 25285 4/0/0 CNAME
rc.yahoo.com., CNAME rc.g01.yahoodns.net., CNAME any-rc.a01.yahoodns.net., A
77.238.178.122 (133)
Using "strict-order" seems to stop the parallel requests, but I guess if the
nameserver were down it wouldn't benefit from the older behaviour which seemed
to be "sticky"
Whenever I ask these questions it turns out to be a failure to read the manual
correctly, so I did have a good gander and raid google first...
Note, if there is no explicit option for this then I think "strict-order" is
actually satisfactory as a workaround!
Many thanks
Ed W
