IPv6 DNS LAC NIC VII October 26, 2004 Wilfried

topics IPv6 specific RR types, status DNS server resolver interaction Operating systems Installation Example configuration snippets

IPv6 specific RR types IPv4 Afor Name to Address (name ==> 32 bits) CNAMEfor "Alias" (name=>name, recursion CNAMEfor "Alias" (name=>name, recursion limited to 1 level) IPv6 AAAAfor Name to Address (name ==> 128 bits) AAAAfor Name to Address (name ==> 128 bits) A6for partial Name to Addr. (0-128 bits) A6for partial Name to Addr. (0-128 bits) DNAMEsimilar to CNAME, but partial replace, DNAMEsimilar to CNAME, but partial replace, multiple level recursion Caution: A6 and DNAME demoted to experimental

IPv6 specific server/resolver Query and Reply Interactions? Content vs. Transport: Content vs. Transport: IPv4 transport only but IPv6-specific RRs OK, IPv4 transport only but IPv6-specific RRs OK, requires recent bind version, dual-stack. Treewalk works with existing servers. IPv6 transport only? IPv6 transport only? Requires recent bind version. Treewalk does NOT work with existing root and (most^H^H^H^Hmany) TLD-Servers! [to change soon?! ==> ICANN announcments)] Alternate Root Server Testbed Alternate Root Server Testbed IPv6 and DNSsec enabled.

Operating Systems FreeBSD 4.4 (and more recent) Mac OS X Mac OS XAIX Solaris 8 Various Linux distributions...other OSs soon or do include support already

Installation bind (better: bind 9.3.x) enable-ipv6 (default is autodetect, should work)./configure --enable-ipv6 (default is autodetect, should work) make make make install make install

AAAA records $ORIGIN example.com host13600INAAAA3ffe:8050:201:1860:42::1 host23600INAAAA3ffe:8050:201:1860:42::2

Reverse lookup (nibble format) Deprecated, but still widely used subtree: ip6.int $ORIGIN e.f.f.3.ip6.int \ 14400INPTRhost1.example.com \ 14400INPTRhost2.example.com New tree, but not necessarily supported by "regular" resolver libraries: ip6.arpa !!! $ORIGIN e.f.f.3.ip6.arpa.

Reverse lookup (bitstrings) $ORIGIN \[x3ffe /64].ip6.arpa. \[x ] 14400IN PTRhost1.example.com \[x ] 14400IN PTRhost2.example.com Shorter records, but difficult to understand; new versions of bind do not necessarily support this format

IPv6 specific configuration IPv4 listen-on { ; }; IPv6 listen-on-v6 { 1:1:1:1:1:1:1:1; };

IPv6 specific configuration IPv4 listen-on port 1234 { ! ; ! ; 1.2.3/24; 1.2.3/24; }; }; IPv6 listen-on-v6 port 777 { 2:2:2:2:2:2:2:2; 2:2:2:2:2:2:2:2; }; };

IPv6 specific configuration IPv4 query-source port * address ; IPv6 query-source-v6 address 8:7:6:5:4:3:2:1 port *;

IPv6 specific configuration IPv4 transfer-source ; IPv6 transfer-source-v6 4:3:2:1:5:6:7:8;