查看: 8491|回复: 0

ISC发布BIND 9.8.0-P1版本支持DNS64特性

满天星 发表于 2011-5-9 21:55:55 | 显示全部楼层 |阅读模式
2011年4月份,IETF正式将DNS64、NAT64等相关特性由Draft文档变为RFC,不仅仅涉及DNS64和NAT64,与此相关联的是一系列的RFC和解决方案,它们是IPv4与IPv6网络过渡与共存时期的重要解决方案,也是继IETF废除NAT-PT[RFC 2766]之后的一项新的过渡方案。
而ISC也继IETF之后,迅速在5月初发布了相应支持DNS64功能的BIND 9.8.0-P1版本。
New Features in BIND 9.8
DNS64 is a transition mechanism to IPv6 deployment. It is one of several options available to ISPs and other providers to ease deployment issues surrounding IPv6

ISC and IPv6
BIND 9 has provided full support for IPv6 resource records ("AAAA") since they were defined, and provides full support for operation over IPv6 transport, alone or on a dual-stack host. BIND 9.8 also includes DNS64, a feature used with an IPv6/IPv4 translator (NAT64) to enable client-server communication between an IPv6-only client and an IPv4-only server without any changes to either one

Download ISC Software

  1. [ dns64 IPv6-prefix {
  2. [ clients { address_match_list }; ]
  3. [ mapped { address_match_list }; ]
  4. [ exclude { address_match_list }; ]
  5. [ suffix IPv6-address; ]
  6. [ recursive-only yes_or_no; ]
  7. [ break-dnssec yes_or_no; ]
  8. }; ];
  9. [ dns64-server name ]
  10. [ dns64-contact name ]
dns64 This directive instructs named to return mapped IPv4 addresses to AAAA queries when there
are no AAAA records. It is intended to be used in conjunction with a NAT64. Each dns64 defines
one DNS64 prefix. Multiple DNS64 prefixes can be defined.
Compatible IPv6 prefixes have lengths of 32, 40, 48, 56, 64 and 96 as per RFC 6052.
Additionally a reverse IP6.ARPA zone will be created for the prefix to provide a mapping from
the IP6.ARPA names to the corresponding IN-ADDR.ARPA names using synthesized CNAMEs.
dns64-server and dns64-contact can be used to specify the name of the server and contact for the
zones. These are settable at the view / options level. These are not settable on a per-prefix basis.
Each dns64 supports an optional clients ACL that determines which clients are affected by this
directive. If not defined, it defaults to any;.
Each dns64 supports an optional mapped ACL that selects which IPv4 addresses are to be mapped
in the corresponding A RRset. If not defined it defaults to any;.
Each dns64 supports an optional exclude ACL that selects which IPv6 addresses will be ignored
for the purposes of determining whether dns64 is to be applied. Any non-matching address will
prevent further DNS64 processing from occurring for this client.
A optional suffix can also be defined to set the bits trailing the mapped IPv4 address bits. By
default these bits are set to ::. The bits matching the prefix and mapped IPv4 address must be
  1. acl rfc1918 { 10/8; 192.168/16; 172.16/12; };
  2. dns64 64:FF9B::/96 {
  3. clients { any; };
  4. mapped { !rfc1918; any; };
  5. exclude { 64:FF9B::/96; ::ffff:0000:0000/96; };
  6. suffix ::;
  7. };
Framework for IPv4/IPv6 Translation:RFC 6144
IP/ICMP Translation Algorithm:RFC 6145
Stateful NAT64: Network Address and Protocol Translation  from IPv6 Clients to IPv4 Servers:RFC 6146
DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers:RFC 6147
IPv6 Addressing of IPv4/IPv6 Translators:RFC 6052
您需要登录后才可以回帖 登录 | 注册


Archiver|手机版|小黑屋|IPv6BBS ( 京ICP备13024693号 | 京公网安备11010802012238 )

GMT+8, 2020-11-25 01:28 , Processed in 0.018943 second(s), 17 queries .

Powered by Discuz! X3.4

Copyright © 2001-2020, Tencent Cloud.

快速回复 返回顶部 返回列表