|
IPv6 forward DNS Entries
![[ch]](/s/countries/ch.gif) Shadow Hawkins on Tuesday, 27 July 2004 23:45:39
Folks,
I'm a bit lost with DNS entries for ipv6 DNS.
I've got no idea how to set up a DNS server as forward ipv6 lookup
in my zone file I have:
$ORIGIN .
$TTL 86400 ; 1 day
delouw.ch IN SOA ns1.bitheads.ch. luc.delouw.ch. (
2004072700 ; serial
60 ; refresh (3 hours)
60 ; retry (1 hour)
60 ; expire (1 week)
60 ; minimum (1 day)
)
IN NS ns1.bitheads.ch.
IN NS ns2.bitheads.ch.
IN MX 10 smtp1.bitheads.ch.
IN MX 20 smtp2.bitheads.ch.
A 213.239.194.21
$ORIGIN delouw.ch.
[..]
ipv6 IN AAAA 2001:6f8:900:20d::2
For me this "looks" fine, but it does not work. Any hints? Thanks a lot
rgds
Luc
IPv6 forward DNS Entries
$ dig @ns1.bitheads.ch ipv6.delouw.ch any
returns NXDOMAIN, thus it doesn't exist, SOA = 2004072701.
As both ns1+ns2.bitheads.ch are BIND 9.2.2 they should support IPv6 records and even IPv6 transport. Are you sure that you don't have any odd $ORIGIN statements in there putting the ipv6 label in a different subdomain? AXFR doesn't work, thus I can't check.
Also check:
DNSReport
you have some odd values for retry, refresh, expire and minimum, the values behind the comment above don't match up. Then again you are probably updating it now, then still, use 'dig @host label type' which is more accurate.
IPv6 forward DNS Entries
Shadow Hawkins on Thursday, 29 July 2004 00:14:19
Thanks for your answer...
The ORIGIN stuff "should" be correct. But I have to admit, that my DNS knowledge is not very high :-\
I know, the time entries are far too short, but for testing it is nice...
Here is a shortend AXFR:
joshua:/var/lib/named/master # dig @localhost delouw.ch AXFR
; <<>> DiG 9.2.2 <<>> @localhost delouw.ch AXFR
;; global options: printcmd
delouw.ch. 86400 IN SOA ns1.bitheads.ch. luc.delouw.ch. 2004072809 60 60 60 60
delouw.ch. 86400 IN NS ns1.bitheads.ch.
delouw.ch. 86400 IN NS ns2.bitheads.ch.
delouw.ch. 86400 IN MX 10 smtp1.bitheads.ch.
delouw.ch. 86400 IN MX 20 smtp2.bitheads.ch.
delouw.ch. 86400 IN A 213.239.194.21
ftp.delouw.ch. 86400 IN A 213.239.194.16
home.delouw.ch. 86400 IN CNAME delouw.homeunix.org.
[..]
ipv6.delouw.ch. 86400 IN AAAA 2001:6f8:900:20d::2
jokes.delouw.ch. 86400 IN A 213.239.194.21
mail.delouw.ch. 86400 IN A 213.239.194.16
ns.delouw.ch. 86400 IN A 213.239.194.16
ns1.delouw.ch. 86400 IN A 213.239.194.16
ns2.delouw.ch. 86400 IN A 213.239.194.17
test.delouw.ch. 86400 IN A 213.239.194.21
[..]
delouw.ch. 86400 IN SOA ns1.bitheads.ch. luc.delouw.ch. 2004072809 60 60 60 60
;; Query time: 3 msec
;; SERVER: 127.0.0.1#53(localhost)
;; WHEN: Thu Jul 29 00:01:45 2004
;; XFR size: 27 records
Rgds
Luc
IPv6 forward DNS Entries
Don't touch it... it works now :)
$ dig ipv6.delouw.ch aaaa | grep AAAA
;ipv6.delouw.ch. IN AAAA
ipv6.delouw.ch. 86391 IN AAAA 2001:6f8:900:20d::2
IPv6 forward DNS Entries
Shadow Hawkins on Thursday, 29 July 2004 19:46:21
Thanks a lot :-)
It looks like I did not understood how ipv6 enabled programs are looking up IP Adresses.
I was always trying with dig ipv6.delouw.ch with the result of now returned value...
Now it looks for me that this kind of software looks first for a AAAA record before the A record. Correct?
Maybe something worth to add in the FAQ?
rgds
Luc
|
on Wednesday, 28 July 2004 08:53:08
Posting is only allowed when you are