BIND 8 bug? (Protocol not supported)

[Pavel V. Knyazev]

<Mark_Andrews at isc.org> wrote:

> > It seems to me your patch helped resolving NS RRs
> > of 194.in-addr.arpa zone, but i'm still having problems
> > contacting a particular site:
> >
> > 5:45pm phobos:src# dig 194.in-addr.arpa ns @ns.ripe.net
> >
> > ; <<>> DiG 8.3 <<>> 194.in-addr.arpa ns @ns.ripe.net
> > ; (2 servers found)
> > ;; res options: init recurs defnam dnsrch
> > ;; res_nsend: Protocol not supported
> > 5:45pm phobos:src#
> >
> > I forgot to mention - i don't have any IPv6 interfaces.
>
> Try the following.
>
> Index: lib/resolv/res_send.c

Much better. I can now dig 194.in-addr.arpa ns @ns.ripe.net.
Of course dig 194.in-addr.arpa ns also works. Thank you.

However, i found that original BIND 8.4.4 also has this bug.
The only difference is that it doesn't show IPv6 IN A RRs
in the ADDITIONAL SECTION until it's asked for IN A
RRs for one or another site (BIND 8 shows IPv6 RRs after
a while even if i don't ask for it). But it still shows me $subj$
if i address to ns.ripe.net for example.

www.isc.org says "BIND 8.4.4 is the latest version of ISC BIND 8"
and i saw the same thing for 8.3.7. Is ISC going to rework under this
buggy code in BIND 8 or any development of BIND 8 is already off?

> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org

--
Pavel V. Knyazev