BIND9 & IPv6

[Gary McAfee]

If his dig client is from BIND 9 and he's querying a BIND 9 server, it
should work with a bitstring label.  You don't have to use the nibble
format.  I did make one assumption, which is that his reverse address is in
the ip6.arpa domain, and your example shows an ip6.int domain query.
Either way, you can query both of them using the bitstring format like I
had in the previous append. See my results, below.  I have a bogus IPv6
address coded in the ip6.arpa domain, but not in the ip6.int domain.  So
you'll see the ip6.arpa query work and the ip6.int query will fail.  But
the point is that you will see the proper query formed by dig in both cases
using the bitstring format if you give dig the proper options.

>dig @localhost -x abcd::1
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49597
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;\[xABCD0000000000000000000000000001/128].ip6.arpa. IN PTR
;; ANSWER SECTION:
\[xABCD0000000000000000000000000001/128].ip6.arpa. 86400 IN PTR
example.ibm.com.
;; AUTHORITY SECTION:
ip6.arpa.               86400   IN      NS      mvsw.tcp.raleigh.ibm.com.
;; Query time: 5 msec
;; SERVER: 127.0.0.1#53(localhost)
;; WHEN: Fri Jun 22 16:00:59 2001
;; MSG SIZE  rcvd: 104

=======================================================
and this for the ip6.int domain query
=======================================================

>dig @localhost -n -x abcd::1
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49597
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.c.b.a.ip6.int.
IN PTR

Regards,
Gary




Bill Manning <bmanning at ISI.EDU>@isc.org on 06/22/2001 03:30:54 PM

Sent by:  bind-users-bounce at isc.org


To:   Gary McAfee/Raleigh/IBM at IBMUS
cc:   extml at ndsoftware.net (NDSoftware), bind-users at isc.org
Subject:  Re: BIND9 & IPv6




%
%
%
% Assuming your zone loaded properly, it looks like your problem is the way
% you used the dig command.  Take a look at the question formed from the
% command you entered.  It created a lookup for an 'A' record-- not the
'PTR'
% record you wanted to look up.  The correct syntax would be 'dig
@servername
% -x 3ffe:80e8:120::1'
%
% Regards,
% Gary
%
%

dig won't work that way for IPv6.  you have to do it this way (feature
enhancement request has already been submitted to Nominum...:)

dig @servername
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.1.0.8.e.0.8.e.f.f.3.ip6.int.

fun eh?

--
--bill