ipv6 BIND reverse lookup question/problem

[Bryce Burgess (bburgess)]

I don't get an "ANSWER SECTION" part of the response to a 'dig -x' cmd
for the reverse lookup for IPV6 addresses. I do for IPV4.
Is the format of the reverse ipv6 not correct?
Webmin automatically gen's the green and will not allow the blue data
below to be entered (complains of invalid data when attempting to save).
I'd assume this green  format is correct (since the webmin util gen'd
it), but the 'dig -x' does not return an "ANSWER" section. Shouldn't it?
or is this normal? 
The green  seems to be a mix of two formats, the full fwd ipv6 address
and appended with the partial reverse arpa data)
 
all the forward lookups seem to be fine (for both ipv4 and ipv6).
 
Should I direct my questions to webmin community?
 
thx,
ice.burge
 
Shouldn't the reverse table entry contain the following:
[
2.5.0.0.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.0.0.0.6.d.f.0.ip6.arpa
]
and not the following:
[
:0fd6:000a:0000:0000:0000:0000:0011:0052.0.0.0.0.0.0.0.0.a.0.0.0.6.d.f.0
.ip6.arpa.  ]
 
from Fedore Linux 7 install and webmin 1.441
BIND version 9.4.0,
 
from "BIND DNS Server" within Webmin, went to "module config" and set
IPV6 to yes, applied changes.
created (fwd) domain se070.com
created (rev) domain 10.11.11.0
created (rev) domain  fd6:a::/64
assigned dns address 10.11.11.52 and 'yes' to rev update. noted new
entry in reverse table 
[  52.11.11.10.in-addr.arpa.  ]
 
assigned dns address 10.11.11.52 and 'yes' to rev update. noted new
entry in reverse table 
[
:0fd6:000a:0000:0000:0000:0000:0011:0052.0.0.0.0.0.0.0.0.a.0.0.0.6.d.f.0
.ip6.arpa.  ]
 
from root, I type in:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
[root at a024 bryce]# dig -x fd6:a::11:52
 
; <<>> DiG 9.4.0 <<>> -x fd6:a::11:52
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1342
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
 
;; QUESTION SECTION:
;2.5.0.0.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.0.0.0.6.d.f.0.ip6.arp
a. IN PTR
 
;; AUTHORITY SECTION:
0.0.0.0.0.0.0.0.a.0.0.0.6.d.f.0.ip6.arpa. 38400 IN SOA a024.se070.com.
bburgess.cisco.com. 1232145084 10800 3600 604800 38400
 
;; Query time: 0 msec
;; SERVER: 10.11.11.24#53(10.11.11.24)
;; WHEN: Fri Jan 16 16:53:38 2009
;; MSG SIZE  rcvd: 155
 
[root at a024 bryce]# dig -x 10.11.11.52
 
; <<>> DiG 9.4.0 <<>> -x 10.11.11.52
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9534
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
 
;; QUESTION SECTION:
;52.11.11.10.in-addr.arpa.      IN      PTR
 
;; ANSWER SECTION:
52.11.11.10.in-addr.arpa. 3600  IN      PTR     se070-cm13-02.se070.com.
 
;; Query time: 0 msec
;; SERVER: 10.89.114.40#53(10.89.114.40)
;; WHEN: Fri Jan 16 16:53:50 2009
;; MSG SIZE  rcvd: 79
 
[root at a024 bryce]# 
 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
 
[root at a024 bryce]# dig se070-cm13-02.se070.com aaaa
 
; <<>> DiG 9.4.0 <<>> se070-cm13-02.se070.com aaaa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51165
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
 
;; QUESTION SECTION:
;se070-cm13-04.se070.com.       IN      AAAA
 
;; ANSWER SECTION:
se070-cm13-02.se070.com. 38400  IN      AAAA    fd6:a::11:52
 
;; AUTHORITY SECTION:
se070.com.              38400   IN      NS      a024.se070.com.
 
;; Query time: 0 msec
;; SERVER: 10.11.11.24#53(10.11.11.24)
;; WHEN: Fri Jan 16 16:39:33 2009
;; MSG SIZE  rcvd: 88
 
[root at a024 bryce]# 
 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20090117/634a66a9/attachment.html>