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"> 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">
Download presentation
Presentation is loading. Please wait.
Published byAustin Guthrie Modified over 11 years ago
1
IPv6 DNS LAC NIC VII October 26, 2004 Wilfried Woeberwoeber@cc.univie.ac.at
2
topics IPv6 specific RR types, status DNS server resolver interaction Operating systems Installation Example configuration snippets
3
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
4
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. bmanning@isi.edu
5
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
6
Installation bind 9.2.0 (better: bind 9.3.x) http://www.isc.org/ http://www.isc.org/installation./configure --enable-ipv6 (default is autodetect, should work)./configure --enable-ipv6 (default is autodetect, should work) make make make install make install
7
AAAA records $ORIGIN example.com host13600INAAAA3ffe:8050:201:1860:42::1 host23600INAAAA3ffe:8050:201:1860:42::2
8
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\ 14400INPTRhost1.example.com 2.0.0.0.0.0.0.0.0.0.0.0.2.4.0.0\ 14400INPTRhost2.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.
9
Reverse lookup (bitstrings) $ORIGIN \[x3ffe805002011860/64].ip6.arpa. \[x0042000000000001] 14400IN PTRhost1.example.com \[x0042000000000001] 14400IN PTRhost2.example.com Shorter records, but difficult to understand; new versions of bind do not necessarily support this format
10
IPv6 specific configuration IPv4 listen-on { 5.6.7.8; }; IPv6 listen-on-v6 { 1:1:1:1:1:1:1:1; };
11
IPv6 specific configuration IPv4 listen-on port 1234 { !1.2.3.4; !1.2.3.4; 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; }; };
12
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 *;
13
IPv6 specific configuration IPv4 transfer-source 10.0.0.5; IPv6 transfer-source-v6 4:3:2:1:5:6:7:8;
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.