When I log in to the ISPConfig3 web console from my laptop on the same LAN and check the settings under System --> Server Config --> DNS tab BIND User : named BIND Group : named BIND zonefiles directory : /var/named BIND named.conf path : /etc/named.conf : /etc/named.conf.local The last entry is "/etc/named.conf.local" does not have a label. After I created the first zone ISPConfig3 did create the file /etc/named.conf.local. Then when I tried to manually start BIND "/etc/init.d/named start" I receive the error : Error in named configuration: /etc/named.conf:42: open: /etc/named.conf.local: file not found ISPConfig3 created this file so why can't it find it? If I cd to /etc and run "ls -l named*" to get a directory listing I get: -rw-r----- 1 root named 964 Jul 7 08:33 named.conf -rw-r--r-- 1 root named 964 Jul 7 08:33 named.conf.local -rw-r--r--. 1 root named 964 Jul 7 08:33 named.iscdlv.key -rw-r-----. 1 root named 964 Jul 7 08:33 named.rfc1912.zones Notice the "." at the end of the permissions list. What does this indicate and is the problem that the "named.conf.local" does not have a "." in the permissions list? Also, since the ISPConfig3 configuration had the BIND owner and group as "named" I changed the group on the named.* files to "named" and tried to restart named but received the same error, named still will not start.