>>>>> On Thu, 24 Oct 2002 14:01:58 -0300,
>>>>> "Juan Luis Baptiste" <[EMAIL PROTECTED]> said:
>> One way of checking reverse is ask for
>> 2.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.0.0.0.2.0.0.0.1.e.c.1.e.f.f.3.IP6.INT.
>> instead of the IPv6 sintax stile.
> I tried that but didn't work either...
The configuration (in the previous message) looks correct. I suspect
it was just because you are not delegated the reverse zone
0.0.2.0.0.0.0.0.2.0.0.0.1.e.c.1.e.f.f.3.IP6.INT correctly.
In fact, in my environment, an upper zone returns an "NXDOMAIN" error
(see below).
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
% dig 0.0.2.0.0.0.0.0.2.0.0.0.1.e.c.1.e.f.f.3.IP6.INT soa
; <<>> DiG 9.2.0 <<>> 0.0.2.0.0.0.0.0.2.0.0.0.1.e.c.1.e.f.f.3.IP6.INT soa
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34629
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;0.0.2.0.0.0.0.0.2.0.0.0.1.e.c.1.e.f.f.3.IP6.INT. IN SOA
;; AUTHORITY SECTION:
2.0.0.0.1.e.c.1.e.f.f.3.IP6.INT. 0 IN SOA mintaka.lcs.mit.edu.
bug-lcs-domain.lcs.mit.edu. 2002102000 7200 3600 2419200 604800
;; Query time: 1324 msec
;; SERVER: 203.178.141.194#53(203.178.141.194)
;; WHEN: Tue Oct 29 16:22:02 2002
;; MSG SIZE rcvd: 135
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
