Date: Mon, 06 May 2002 05:34:12 +0900 From: Hajimu UMEMOTO <ume@mahoroba.org> To: Doug Barton <DougB@FreeBSD.org> Cc: Hajimu UMEMOTO <ume@mahoroba.org>, Makoto Matsushita <matusita@jp.FreeBSD.org>, <stable@FreeBSD.org> Subject: Re: BIND in -stable Message-ID: <ygehelmjpvf.wl@mille.mahoroba.org> In-Reply-To: <20020505131515.M3321-100000@master.gorean.org> References: <ygelmaykfm3.wl@mille.mahoroba.org> <20020505131515.M3321-100000@master.gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
>>>>> On Sun, 5 May 2002 13:16:46 -0700 (PDT)
>>>>> Doug Barton <DougB@FreeBSD.org> said:
> nslookup of BIND 8.3.1 has another problem. If you put IPv6 address
> for nameserver in /etc/resolv.conf, you cannot use nslookup at all.
DougB> A) nslookup is a truly horrible tool, and shouldn't be used by
DougB> anyone, ever. B) While I understand they are important to you, IPv6 issues
DougB> are not important to a substantial majority of our userbase. Also, IPv6
DougB> support in bind 8 is limited anyways. Those how need IPv6 features should
DougB> really be using bind 9.
Yes, those who expect full support of an IPv6 should use BIND9. I
don't mean expecting full support of an IPv6 to BIND8. However, if we
put following lines in /etc/resolv.conf:
nameserver <IPv6 address>
nameserver <IPv4 address>
8.2.X of nslookup simply ignored an IPv6 line and did query to IPv4
address. 8.3.X of nslookup doesn't ignore an IPv6 line due to an IPv6
awareness of libbind and try to query to 0.0.0.0 which is dummy
nsaddr_list entry for an IPv6 entry.
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ygehelmjpvf.wl>