- Using Bind 8 or 9
First of all, you need to determine which version of bind you're running.
It is extremely important that you're running named 8.2.3-REL or later. Previous versions of bind have security holes in them which allow your system to be compromised. ISC is a good place to look at to see if your version has security issues.
Bind 8/9 changed drastically from Bind 4. The first thing is to throw out whatever preconceptions you know about bind. If you previously were using Bind 4, and upgraded to Bind 8, you should first realize that your system will not automatically use Bind 8 until you tell it to. This will become apparent when you try to make changes, and somehow it still uses the old Bind 4 configuration files.
Notice in your /etc/rc.conf file:
Typing "which named" will show you the named that it is invoking
Most likeley it's not invoking /usr/sbin/named, but rather the old bind4 named
Below is an example of mui.net, which hosts itself and another zone, chhawaii.com
The new way of storing your files is as follows:
/etc/namedb/master <----- primary zones are stored in this directory
/etc/namedb/master/12.36.98 <--- in.addr.arpa files
/etc/namedb/master/127.0.0 <--- local reverse files
/etc/namedb/master/chhawaii.com.hosts <--- chhawaii dns information
/etc/namedb/master/mui.net.hosts <------ mui dns information
/etc/namedb/slave <----- secondary zones are stored in this directory
/etc/namedb/named.conf <---- main configuration file
/etc/namedb/named.cache <---- file containing root server information (ftp.rs.internic.net/domain/named.root)