Problem
I used h2n to create a set of DNS configuration files, but the DNS server (named) will not start.
Cause
h2n creates all of its files in the directory you are in when you run it.
The named.conf file h2n creates needs to be in /etc/named.d (OpenServer) or /etc/inet/named.d (UnixWare).
Therefore, before you can start your DNS server you will need to copy the named.conf configuration file created by h2n into:
/etc/named.d (if using OpenServer 6 or OpenServer 5) or /etc/inet/named.d (if UnixWare 7.1.4)
Solution
You can run h2n while in any directory and it will create a set of DNS files for your network.
One of those files is named.conf.The /etc/rc2.d/S85tcp script searches for named.conf in /etc/named.d (OpenServer) or /etc/inet/named.d (UnixWare).
For example, if you create a new directory, /u/dnsconfig, and change into that directory and run h2n, all of your files will be created in /u/dnsconfig.
The named.conf file created will have the correct directory directive pointing to /u/dnsconfig, but you must still manually mv or cp or ln this file to /etc so that the S85tcp script can find it.
Also, you must ensure that the permissions are correct (if you do a
cp) so you can accomplish this with the commands executed from the
/u/dnsconfig directory:# cp named.conf /etc
# chown bin:bin named.conf
# chmod 644 named.confThe named.conf file must be writable (as do the other files for DNS) so that the SCO DNS manager can run and update these.
See also
TA127209, "Setting up a DNS architecture in a stable closed network"
TA127256, "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?"