only thing i can think of is check with other DNS server to resolve DNS.
DNS cahcer in RouterOS is capable to resolve IPv6 addresses correctly (AAAA entries)
Are you sure? It should express itself (more) clearly if it does not get a proper IPv6 address and not just talk about "invalid value...".
For instance on my linux box I get:
[root@haskaa ~]# dig @194.204.0.1 ipv6.google.com AAAA
; <<>> DiG 9.5.2-RedHat-9.5.2-1.fc10 <<>> @194.204.0.1 ipv6.google.com AAAA
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38453
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION:
;ipv6.google.com. IN AAAA
;; ANSWER SECTION:
ipv6.google.com. 9370 IN CNAME ipv6.l.google.com.
ipv6.l.google.com. 300 IN AAAA 2a00:1450:8007::67
ipv6.l.google.com. 300 IN AAAA 2a00:1450:8007::68
ipv6.l.google.com. 300 IN AAAA 2a00:1450:8007::69
ipv6.l.google.com. 300 IN AAAA 2a00:1450:8007::63
ipv6.l.google.com. 300 IN AAAA 2a00:1450:8007::6a
ipv6.l.google.com. 300 IN AAAA 2a00:1450:8007::93
;; AUTHORITY SECTION:
google.com. 332716 IN NS ns4.google.com.
google.com. 332716 IN NS ns1.google.com.
google.com. 332716 IN NS ns2.google.com.
google.com. 332716 IN NS ns3.google.com.
;; ADDITIONAL SECTION:
ns2.google.com. 328879 IN A 216.239.34.10
ns1.google.com. 339651 IN A 216.239.32.10
ns4.google.com. 342174 IN A 216.239.38.10
ns3.google.com. 344571 IN A 216.239.36.10
;; Query time: 46 msec
;; SERVER: 194.204.0.1#53(194.204.0.1)
;; WHEN: Fri Jun 4 19:22:16 2010
;; MSG SIZE rcvd: 358
[root@haskaa ~]# dig @194.204.22.2 ipv6.google.com AAAA
; <<>> DiG 9.5.2-RedHat-9.5.2-1.fc10 <<>> @194.204.22.2 ipv6.google.com AAAA
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10469
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION:
;ipv6.google.com. IN AAAA
;; ANSWER SECTION:
ipv6.google.com. 9219 IN CNAME ipv6.l.google.com.
ipv6.l.google.com. 264 IN AAAA 2a00:1450:8007::63
ipv6.l.google.com. 264 IN AAAA 2a00:1450:8007::67
ipv6.l.google.com. 264 IN AAAA 2a00:1450:8007::68
ipv6.l.google.com. 264 IN AAAA 2a00:1450:8007::69
ipv6.l.google.com. 264 IN AAAA 2a00:1450:8007::6a
ipv6.l.google.com. 264 IN AAAA 2a00:1450:8007::93
;; AUTHORITY SECTION:
google.com. 159690 IN NS ns4.google.com.
google.com. 159690 IN NS ns1.google.com.
google.com. 159690 IN NS ns3.google.com.
google.com. 159690 IN NS ns2.google.com.
;; ADDITIONAL SECTION:
ns1.google.com. 159689 IN A 216.239.32.10
ns2.google.com. 159689 IN A 216.239.34.10
ns3.google.com. 159689 IN A 216.239.36.10
ns4.google.com. 159689 IN A 216.239.38.10
;; Query time: 8 msec
;; SERVER: 194.204.22.2#53(194.204.22.2)
;; WHEN: Fri Jun 4 19:22:23 2010
;; MSG SIZE rcvd: 358
[root@haskaa ~]#
But my MT box (MikroTik RouterOS 5.0beta2) has errors with the same DNS servers:
[admin@Ranume] /ip dns> export
# jun/04/2010 20:44:09 by RouterOS 5.0beta2
# software id = LB5I-W12K
#
/ip dns
set allow-remote-requests=no cache-max-ttl=1w cache-size=2048KiB \
max-udp-packet-size=512 servers=194.204.0.1,194.204.22.2
[admin@Ranume] /ip dns> /ping ipv6.google.com
invalid value for argument address
[admin@Ranume] /ip dns>
What is really wrong with it?