Problem
The latest maintenance release for my SCO Unix server
upgraded bind from an earlier version to bind9. What
issues might I need to consider when migrating to a later
bind version? Solution
BIND8 to BIND9 Migration Technical Article:
------------------------------------------There are several migration issues that you may encounter when upgrading from bind8 to bind9 like handling of configuration errors, logging, case sensitivity in ACL names, zone file compatibility etc. These are covered in <http://www.sco.com>. Here are few more tips and suggestions when migrating to bind9.
1. bind9 named would not start if there are configuration error in contrast to bind8 which continued after config file errors. You can run named-checkconf to ensure syntactic correctness. For example, if you have an include directive like the one below
include /etc/named.d/.security.d/key.includeand the key.include file does not exist, then bind8 named would still start and continue to operate with partial configuration. In bind9 an error would be reported and named would fail to start. In such cases, name-checkconf can help in determining the error.
2. When setting up a caching nameserver, its possible that nslookup/dig command may refuse the request when accessed from another subnet within the local domain.
The default option in bind8 was to allow access to anyone.
This is not the case in bind9.
In bind9, there are additional access control options when responding to queries from such clients.
In particular there is an "allow-query" and "allow-query-cache" options that may need to be configured when setting up the nameserver.
In this particular case, we need to setup the "allow-query-cache" option to "any" when wanting to answer across subnets.
The default value for this option is "localhost" and "localnets".
This is why when an nslookup is done from the same subnet as the caching nameserver the lookup is successful.
The following example would illustrate the required configuration in bind9.
options { directory "/etc/named.d"; allow-query { mynets; }; forwarders {132.147.103.12; 132.147.210.8; 132.147.210.7;}; };
acl mynets {
132.147.135.0/24; 132.147.167.0/24;
};You can also set the options primitive as follows without the need for an acl primitive.
options { directory "/etc/named.d"; allow-query-cache { any; }; forwarders {132.147.103.12; 132.147.210.8; 132.147.210.7;}; };
In bind8, it was not necessary to specify the acl or the allow-query primitive.
3. There are several source of information that may help migrate from bind8. These are collected from the web
http://uw714doc.xinuos.com/en/NET_tcpip/dnsN.main.html#dns.bind8-9notes
http://www.isc.org/files/Bv9.4ARM.pdf
http://www.isc.org/software/bind/documentation
http://www.apnic.net/meetings/10/programme/presentations/Mathias-DNS-Tutorial.ppt See also
TA127234, "h2n Creates files but named won't start"TA127209, "Setting up a DNS architecture in a stable closed network"