On 16-Dec-12 16:12, NLnet Labs via RT wrote:
Show quoted text> <URL:
https://rt.cpan.org/Ticket/Display.html?id=79569 >
>
> On Thu 13 Sep 2012 08:47:57, NLNETLABS wrote:
>> It should. Looking at the code I see that axfr is only tried from the
>> first nameserver as well. This has to be fixed too.
> Setting answerfrom is fixed since 0.69. As for the using only the first
> nameserver; Perhaps that is too much intelligence for
> Net::DNS::Resolver. We are not trying to implement a full top-quality
> resolver in perl. You could also easily shift or shuffle nameservers on
> axfr failure yourself.
>
> Thank you for reporting,
>
> -- Willem
Thanks for fixing answerfrom. As for not using all the nameservers -
that wasn't in my report; a developer noted that. when he took a first
look at my report.
However, Net::DNS does iterate over all nameservers in other parts of
the code - why not be consistent? It's hard to justify that axfr is
different from query or update... and as I noted in another bug report,
with IPv6 finally coming on-line, hosts with multiple addresses and user
connectivity to only some of them will be more common, not less.
--
This communication may not represent my employer's views,
if any, on the matters discussed.
RT for rt.cpan.org