dig +trace failure
My 9.6.1-P1 dig programs (HP-UX and Linux) rather consistently fail when trying to trace the delegation of 231.84.192.IN-ADDR.ARPA. Out of curiousity, are others from different places on the Internet able to duplicate the failure? dig +trace 231.84.192.in-addr.arpa ; <<>> DiG 9.6.1-P1 <<>> +trace 231.84.192.in-addr.arpa ;; global options: +cmd . 431482 IN NS A.ROOT-SERVERS.NET. . 431482 IN NS J.ROOT-SERVERS.NET. . 431482 IN NS B.ROOT-SERVERS.NET. . 431482 IN NS D.ROOT-SERVERS.NET. . 431482 IN NS E.ROOT-SERVERS.NET. . 431482 IN NS H.ROOT-SERVERS.NET. . 431482 IN NS M.ROOT-SERVERS.NET. . 431482 IN NS L.ROOT-SERVERS.NET. . 431482 IN NS F.ROOT-SERVERS.NET. . 431482 IN NS G.ROOT-SERVERS.NET. . 431482 IN NS C.ROOT-SERVERS.NET. . 431482 IN NS K.ROOT-SERVERS.NET. . 431482 IN NS I.ROOT-SERVERS.NET. ;; Received 272 bytes from 15.243.224.30#53(15.243.224.30) in 1 ms 192.in-addr.arpa. 86400 IN NS Y.ARIN.NET. 192.in-addr.arpa. 86400 IN NS Z.ARIN.NET. 192.in-addr.arpa. 86400 IN NS CHIA.ARIN.NET. 192.in-addr.arpa. 86400 IN NS DILL.ARIN.NET. 192.in-addr.arpa. 86400 IN NS BASIL.ARIN.NET. 192.in-addr.arpa. 86400 IN NS HENNA.ARIN.NET. 192.in-addr.arpa. 86400 IN NS INDIGO.ARIN.NET. 192.in-addr.arpa. 86400 IN NS X.ARIN.NET. ;; Received 196 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 299 ms 231.84.192.in-addr.arpa. 86400 IN NS mail.boston.accrue.com. 231.84.192.in-addr.arpa. 86400 IN NS ns1.accrue.com. ;; Received 95 bytes from 192.35.51.32#53(DILL.ARIN.NET) in 144 ms ;; Truncated, retrying in TCP mode. socket.c:2486: REQUIREsock) != ((void *)0)) && (((const isc__magic_t *)(sock))->magic == ((('I') << 24 | ('O') << 16 | ('i') << 8 | ('o')) failed. Aborted -- Andris ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: dig +trace failure
On Wed, Sep 2, 2009 at 8:37 PM, Andris Kalnozols wrote: > My 9.6.1-P1 dig programs (HP-UX and Linux) rather consistently fail > when trying to trace the delegation of 231.84.192.IN-ADDR.ARPA. > Out of curiousity, are others from different places on the Internet > able to duplicate the failure? Same here, bind 9.6.1_P1 ;; Received 196 bytes from 2001:503:ba3e::2:30#53(A.ROOT-SERVERS.NET) in 150 ms 231.84.192.in-addr.arpa. 86400 IN NS ns1.accrue.com. 231.84.192.in-addr.arpa. 86400 IN NS mail.boston.accrue.com. ;; Received 95 bytes from 192.26.92.32#53(HENNA.ARIN.NET) in 62 ms ;; Truncated, retrying in TCP mode. socket.c:2486: REQUIREsock) != ((void *)0)) && (((const isc__magic_t *)(sock))->magic == ((('I') << 24 | ('O') << 16 | ('i') << 8 | ('o')) failed. Aborted -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http://www.ardynet.com:9000/ardymusic.ogg.m3u ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: dig +trace failure
In message <200909030037.raa27...@nasdaq.hpl.hp.com>, Andris Kalnozols writes: > My 9.6.1-P1 dig programs (HP-UX and Linux) rather consistently fail > when trying to trace the delegation of 231.84.192.IN-ADDR.ARPA. > Out of curiousity, are others from different places on the Internet > able to duplicate the failure? It's fixed in the next release. You should be able to verify this using the v9_6 from the BIND Forum CVS repository. Mark > dig +trace 231.84.192.in-addr.arpa > > ; <<>> DiG 9.6.1-P1 <<>> +trace 231.84.192.in-addr.arpa > ;; global options: +cmd > . 431482 IN NS A.ROOT-SERVERS.NET. > . 431482 IN NS J.ROOT-SERVERS.NET. > . 431482 IN NS B.ROOT-SERVERS.NET. > . 431482 IN NS D.ROOT-SERVERS.NET. > . 431482 IN NS E.ROOT-SERVERS.NET. > . 431482 IN NS H.ROOT-SERVERS.NET. > . 431482 IN NS M.ROOT-SERVERS.NET. > . 431482 IN NS L.ROOT-SERVERS.NET. > . 431482 IN NS F.ROOT-SERVERS.NET. > . 431482 IN NS G.ROOT-SERVERS.NET. > . 431482 IN NS C.ROOT-SERVERS.NET. > . 431482 IN NS K.ROOT-SERVERS.NET. > . 431482 IN NS I.ROOT-SERVERS.NET. > ;; Received 272 bytes from 15.243.224.30#53(15.243.224.30) in 1 ms > > 192.in-addr.arpa. 86400 IN NS Y.ARIN.NET. > 192.in-addr.arpa. 86400 IN NS Z.ARIN.NET. > 192.in-addr.arpa. 86400 IN NS CHIA.ARIN.NET. > 192.in-addr.arpa. 86400 IN NS DILL.ARIN.NET. > 192.in-addr.arpa. 86400 IN NS BASIL.ARIN.NET. > 192.in-addr.arpa. 86400 IN NS HENNA.ARIN.NET. > 192.in-addr.arpa. 86400 IN NS INDIGO.ARIN.NET. > 192.in-addr.arpa. 86400 IN NS X.ARIN.NET. > ;; Received 196 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 299 ms > > 231.84.192.in-addr.arpa. 86400 IN NS mail.boston.accrue.com. > 231.84.192.in-addr.arpa. 86400 IN NS ns1.accrue.com. > ;; Received 95 bytes from 192.35.51.32#53(DILL.ARIN.NET) in 144 ms > > ;; Truncated, retrying in TCP mode. > socket.c:2486: REQUIREsock) != ((void *)0)) && (((const isc__magic_t *)(s > ock))->magic == ((('I') << 24 | ('O') << 16 | ('i') << 8 | ('o')) failed. > Aborted > > > -- > Andris > ___ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: dig +trace failure
On Sep 3 2009, Mark Andrews wrote: In message <200909030037.raa27...@nasdaq.hpl.hp.com>, Andris Kalnozols writes: My 9.6.1-P1 dig programs (HP-UX and Linux) rather consistently fail when trying to trace the delegation of 231.84.192.IN-ADDR.ARPA. Out of curiousity, are others from different places on the Internet able to duplicate the failure? It's fixed in the next release. You should be able to verify this using the v9_6 from the BIND Forum CVS repository. I have the fix Mark refers to applied (the bug strikes during fallback to TCP) and get: $ dig +trace 231.84.192.in-addr.arpa ; <<>> DiG 9.6.1-P1 <<>> +trace 231.84.192.in-addr.arpa ;; global options: +cmd . 35116 IN NS I.ROOT-SERVERS.NET. . 35116 IN NS B.ROOT-SERVERS.NET. . 35116 IN NS L.ROOT-SERVERS.NET. . 35116 IN NS C.ROOT-SERVERS.NET. . 35116 IN NS G.ROOT-SERVERS.NET. . 35116 IN NS M.ROOT-SERVERS.NET. . 35116 IN NS E.ROOT-SERVERS.NET. . 35116 IN NS J.ROOT-SERVERS.NET. . 35116 IN NS F.ROOT-SERVERS.NET. . 35116 IN NS A.ROOT-SERVERS.NET. . 35116 IN NS K.ROOT-SERVERS.NET. . 35116 IN NS H.ROOT-SERVERS.NET. . 35116 IN NS D.ROOT-SERVERS.NET. ;; Received 272 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms 192.in-addr.arpa. 86400 IN NS Y.ARIN.NET. 192.in-addr.arpa. 86400 IN NS HENNA.ARIN.NET. 192.in-addr.arpa. 86400 IN NS BASIL.ARIN.NET. 192.in-addr.arpa. 86400 IN NS DILL.ARIN.NET. 192.in-addr.arpa. 86400 IN NS CHIA.ARIN.NET. 192.in-addr.arpa. 86400 IN NS Z.ARIN.NET. 192.in-addr.arpa. 86400 IN NS X.ARIN.NET. 192.in-addr.arpa. 86400 IN NS INDIGO.ARIN.NET. ;; Received 196 bytes from 2001:500:2f::f#53(F.ROOT-SERVERS.NET) in 264 ms 231.84.192.in-addr.arpa. 86400 IN NS mail.boston.accrue.com. 231.84.192.in-addr.arpa. 86400 IN NS ns1.accrue.com. ;; Received 95 bytes from 2001:500:31::63#53(X.ARIN.NET) in 166 ms ;; Truncated, retrying in TCP mode. ;; connection timed out; no servers could be reached No joy if you actually wanted a result, of course. Both nameservers for the zone are u/s. -- Chris Thompson Email: c...@cam.ac.uk ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users