<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFCC" text="#000000">
I am trying to prepare my internal network for IPv6, including the
local DNS-server (caching & Authoritative).<br>
<br>
I have put one single IPv6 address into my normal zone, everything
else is IPv4.<br>
<br>
If I do: dig axfr s-carlsen.dk, I get all addresses, including the
IPv6 address.<br>
<br>
~~~~~~~~<br>
silver4:~ carlsen$ dig axfr s-carlsen.dk<br>
<br>
; <<>> DiG 9.6.0-APPLE-P2 <<>> axfr
s-carlsen.dk<br>
;; global options: +cmd<br>
s-carlsen.dk. 86400 IN SOA ns2.s-carlsen.dk.
hostmaster.s-carlsen.dk. 2010123191 10800 900 604800 86400<br>
s-carlsen.dk. 86400 IN NS ns2.s-carlsen.dk.<br>
s-carlsen.dk. 86400 IN A 192.168.16.32<br>
s-carlsen.dk. 86400 IN MX 10 mail2.s-carlsen.dk.<br>
s-carlsen.dk. 86400 IN MX 20 smtp.fullrate.dk.<br>
s-carlsen.dk. 86400 IN TXT "v=spf1 a mx ptr
ip4:95.166.175.97 include:fullrate.dk include:sonofon.dk ?all"<br>
s-carlsen.dk. 86400 IN SPF "v=spf1 a mx ptr
ip4:95.166.175.97 include:fullrate.dk include:sonofon.dk ?all"<br>
argus.s-carlsen.dk. 86400 IN A 192.168.16.36<br>
argus2.s-carlsen.dk. 86400 IN A 192.168.16.37<br>
argus3.s-carlsen.dk. 86400 IN A 192.168.16.39<br>
d6.s-carlsen.dk. 86400 IN AAAA
2002:5ab9:80d2:1:211:32ff:fe05:bbe9<br>
ds-106e.s-carlsen.dk. 86400 IN A 192.168.16.33<br>
ds-209.s-carlsen.dk. 86400 IN A 192.168.16.34<br>
gw1.s-carlsen.dk. 86400 IN A 192.168.16.1<br>
gw2.s-carlsen.dk. 86400 IN A 192.168.16.2<br>
hermione.s-carlsen.dk. 86400 IN A 192.168.16.35<br>
jeanette.s-carlsen.dk. 86400 IN A 192.168.16.66<br>
mail2.s-carlsen.dk. 86400 IN A 192.168.16.32<br>
nospam.s-carlsen.dk. 86400 IN NS ns2.s-carlsen.dk.<br>
ns2.s-carlsen.dk. 86400 IN A 192.168.16.32<br>
ntp.s-carlsen.dk. 86400 IN A 192.168.16.32<br>
olfert.s-carlsen.dk. 86400 IN A 192.168.16.67<br>
pizza.s-carlsen.dk. 86400 IN A 192.168.16.3<br>
ps3.s-carlsen.dk. 86400 IN A 192.168.16.225<br>
revo.s-carlsen.dk. 86400 IN A 192.168.16.32<br>
samsung.s-carlsen.dk. 86400 IN A 192.168.16.38<br>
silver.s-carlsen.dk. 86400 IN A 192.168.16.64<br>
silver2.s-carlsen.dk. 86400 IN A 192.168.16.65<br>
silver3.s-carlsen.dk. 86400 IN A 192.168.16.68<br>
silver4.s-carlsen.dk. 86400 IN A 192.168.16.69<br>
Squeezebox.s-carlsen.dk. 900 IN A 192.168.16.115<br>
Squeezebox.s-carlsen.dk. 900 IN TXT
"316fde0ad9758b6642fe5e0075846f6fcc"<br>
SqueezeboxContro.s-carlsen.dk. 900 IN A 192.168.16.114<br>
SqueezeboxContro.s-carlsen.dk. 900 IN TXT
"31b1d19028b84d3a2bd80b66469ac5c530"<br>
SqueezeboxRadio.s-carlsen.dk. 900 IN A 192.168.16.116<br>
SqueezeboxRadio.s-carlsen.dk. 900 IN TXT
"3145755df70f188c8e9859a7e4584b3edd"<br>
wii.s-carlsen.dk. 86400 IN A 192.168.16.224<br>
winky.s-carlsen.dk. 86400 IN A 192.168.16.5<br>
<a class="moz-txt-link-abbreviated" href="http://www.s-carlsen.dk">www.s-carlsen.dk</a>. 86400 IN A 192.168.16.32<br>
s-carlsen.dk. 86400 IN SOA ns2.s-carlsen.dk.
hostmaster.s-carlsen.dk. 2010123191 10800 900 604800 86400<br>
;; Query time: 3 msec<br>
;; SERVER: 192.168.16.32#53(192.168.16.32)<br>
;; WHEN: Sun Sep 11 19:59:29 2011<br>
;; XFR size: 40 records (messages 1, bytes 1188)<br>
~~~~~~~~<br>
<br>
If I do: dig d6.s-carlsen.dk (d6 is the host in question, it has
one IPv6 address, nothing else), I get no answer, but it gives me
the SOA. This is the case even if looking from the server itself.<br>
<br>
The following from my normal workstation.<br>
~~~~~~~~<br>
silver4:~ carlsen$ dig d6.s-carlsen.dk<br>
<br>
; <<>> DiG 9.6.0-APPLE-P2 <<>>
d6.s-carlsen.dk<br>
;; global options: +cmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:
45921<br>
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1,
ADDITIONAL: 0<br>
<br>
;; QUESTION SECTION:<br>
;d6.s-carlsen.dk. IN A<br>
<br>
;; AUTHORITY SECTION:<br>
s-carlsen.dk. 86400 IN SOA ns2.s-carlsen.dk.
hostmaster.s-carlsen.dk. 2010123191 10800 900 604800 86400<br>
<br>
;; Query time: 1 msec<br>
;; SERVER: 192.168.16.32#53(192.168.16.32)<br>
;; WHEN: Sun Sep 11 19:53:00 2011<br>
;; MSG SIZE rcvd: 84<br>
~~~~~~~~<br>
<br>
I have a clear feeling that this is a very stupid mistake on my
side, I just don't have any more clues, where to start looking.
Internally, where this is teted, IPv6 connectivity is working ok, if
I put the IPv6 address into the browser, it works fine.<br>
<br>
Suggestions would be welcome.<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>