This is a discussion on Re: BIND 8 bug? (Protocol not supported) within the Bind Users forums, part of the DNS and Related Forums category; <Mark_Andrews@isc.org> wrote: > I suspect you are seeing the side effects of this which will > ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
<Mark_Andrews@isc.org> wrote:
> I suspect you are seeing the side effects of this which will > only be visible on timeouts if you only have a single nameserver > in resolv.conf. > > 1594. [bug] if only a single nameserver was listed in resolv.conf > IPv6 default server was also being used. So it is related to a resolver, not named? Paraphrasing, may i leave original 8.3.7-REL on its place and everything's gonna be allright, or do i have to update named? There will be no local users on this server. Just a single named process serving customers' queries. 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. > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@isc.org -- Pavel V. Knyazev |
![]() |
| Thread Tools | |
| Display Modes | |
|
|