130 likes | 262 Vues
This document explores IPv6-specific resource record types in DNS, detailing their status and operational characteristics including query and reply interactions. It covers installation examples and configuration snippets for various operating systems like FreeBSD, Mac OS X, AIX, Solaris, and Linux distributions. The content addresses AAAA, A6, and DNAME records, along with reverse lookup mechanisms. It emphasizes the need for recent versions of BIND and discusses important considerations for dual-stack environments. This guide serves as a practical resource for network administrators working with IPv6 DNS.
E N D
IPv6 DNS LACNICVII October 26, 2004 Wilfried Woeberwoeber@cc.univie.ac.at
IPv6 specific RR types, status DNS server <=> resolver interaction Operating systems Installation Example configuration snippets topics
IPv4 A for Name to Address (name ==> 32 bits) CNAME for "Alias" (name=>name, “recursion“ limited to 1 level) IPv6 AAAA for Name to Address (name ==> 128 bits) .................................................... A6 for partial Name to Addr. (0-128 bits) DNAME similar to CNAME, but partial replace, multiple level “recursion“ Caution: A6 and DNAME demoted to “experimental“ IPv6 specific RR types
Query and Reply Interactions? Content vs. Transport: IPv4 transport only but IPv6-specific RRs OK, requires recent bind version, dual-stack. Treewalk works with existing servers. 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 IPv6 and DNSsec enabled. bmanning@isi.edu IPv6 specific server/resolver
FreeBSD 4.4 (and more recent) Mac OS X AIX Solaris 8 Various Linux distributions ...other OSs soon or do include support already Operating Systems
bind 9.2.0 (better: bind 9.3.x) http://www.isc.org/ installation ./configure --enable-ipv6(default is autodetect, should work) make make install Installation
AAAA records $ORIGIN example.com host1 3600 IN AAAA 3ffe:8050:201:1860:42::1 host2 3600 IN AAAA 3ffe:8050:201:1860:42::2
Reverse lookup (nibble format) Deprecated, but still widely used subtree: ip6.int $ORIGIN 0.6.8.1.1.0.2.0.0.5.0.8.e.f.f.3.ip6.int. 1.0.0.0.0.0.0.0.0.0.0.0.2.4.0.0 \ 14400 IN PTR host1.example.com 2.0.0.0.0.0.0.0.0.0.0.0.2.4.0.0 \ 14400 IN PTR host2.example.com New tree, but not necessarily supported by "regular" resolver libraries: ip6.arpa !!! $ORIGIN 0.6.8.1.1.0.2.0.0.5.0.8.e.f.f.3.ip6.arpa.
Reverse lookup (bitstrings) $ORIGIN \[x3ffe805002011860/64].ip6.arpa. \[x0042000000000001] 14400 IN PTR host1.example.com \[x0042000000000001] 14400 IN PTR host2.example.com Shorter records, but difficult to understand; new versions ofbinddo not necessarily support this format
IPv4 listen-on { 5.6.7.8; }; IPv6 listen-on-v6 { 1:1:1:1:1:1:1:1;}; IPv6 specific configuration
IPv4 listen-on port 1234 { !1.2.3.4; 1.2.3/24; }; IPv6 listen-on-v6 port 777 { 2:2:2:2:2:2:2:2; }; IPv6 specific configuration
IPv4 query-source port * address 10.0.0.54 ; IPv6 query-source-v6 address 8:7:6:5:4:3:2:1 port *; IPv6 specific configuration
IPv4 transfer-source 10.0.0.5; IPv6 transfer-source-v6 4:3:2:1:5:6:7:8; IPv6 specific configuration