This issue was initially reported to me by a customer running CentOS 5.5 x86_64. I was able to duplicate it on CentOS 5.5 i386 with dig version: DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2
When doing a dig +trace to a DNSBL for a TXT record they're getting a segfault after making the final query (prior to displaying the answer). I did a tcpdump of this behavior and saw two identical queries from the same source port with the same transaction ID 0.000074 seconds apart. The responses were received 0.000745 seconds apart, from the same IP with the same transaction ID. When I repeat the test through an intermediary resolver it only sends one query datagram and gets a single response (and doesn't crash). Any ideas? -- bk _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
