The following lists the limitations in BIND 9.2.0:
Specific IPv6
addresses cannot be specified with the listen-on-v6 option.
The rndc dump.db command dumps only the cache information. You can
run dig axfr <domain> command to obtain the db file information.
In IPv6 systems, the
notify directive in the Options statement in named.conf will be successful only if there is an IPv4-mapped-IPv6 address
in the masters clause of the slave zone.
To set up forwarding nameservers,
db.<prefix>.IP6.INT files need to be created manually. Currently,
db.<prefix>.IP6.INT files are not being created. For example: for
IPv6 address fe80::1/16, the db file db.0.8.e.f.IP6.INT, should be created and named.conf should be changed accordingly.
In IPv6 systems, the ACLs
may not produce desired results if an IPv4 address is specified
in the ACL entry.
An IPv4-mapped-IPv6 address needs to be specified instead
of the IPv4 address in the ACL entry as follows:
acl egacl { ::ffff:15.70.128.34:};
In nslookup, the ‘ls’ command is used to list the information available
for domain, optionally creating or appending to filename. The output
of this command contains host names and their Internet addresses.
The AAAA records are not shown in this output.
The “server” option in nslookup does not work for
IPv6 addresses if the name server specified in /etc/resolv.conf is an IPv4 server. This option will not work for
IPv4 addresses if the name server is specified in /etc/resolv.conf is an IPv6 server.
The command used to revert
back to the previous version of BIND (i.e., 9.2.0), “
/usr/bin/enable_inet -r bind” must not be executed in the directory “
/usr/contrib/bind/save_custom/” or in any of its sub-directories.
