Matus UHLAR - fantomas wrote:
I strongly recommend you upgrading the BIND first. Later versions issue that
message much less often.
if the only reason is the fix mentioned by Mark
2504. [bug] Address race condition in the socket code.
then that doesn't explain why my small manual sample of 20 such
queries resulted in dig reporting "timeout" for virtually all of them.
These involved lame delegations to non-responsive nameservers.
plus the ARM itself says the current behaviour needs to be changed
Note: eventually named will have to stop treating such timeouts as
due to
RFC 1034 non compliance and start treating it as plain packet loss.
Falsely
classifying packet loss as due to RFC 1034 non compliance impacts on
DNSSEC
validation which requires EDNS for the DNSSEC records to be returned.
since this was 9.6 ARM p41, I assume the change has not yet happened
but yes, we are about to start an upgrade cycle to 9.6.0-P2
when I will re-enable edns reporting and do another manual sample.
Danny
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
