After the configuration of a DNS server in a site is modified, the DNS named process fails to start during verification. - The path to the named files is not specified in the inetsvc file.
- The host name in the hosts file is different from the host name in the hostname.qfe1 file.
- The configuration or format of the named.conf file is incorrect.
- The format of every zone file is incorrect.
- Check whether the inetsvc file is normal.
This file is automatically executed during the startup of the system. Be sure to check whether the path is specified in the named file. You can find that the path to the named file is correct. # vi /etc/init.d/inetsvc Check the following fields: if [ -f /usr/local/sbin/named -a -f /etc/named.conf ]; then echo starting internet domain name server. /usr/local/sbin/named & fi - Check whether the files hosts and hostname.qfe1 are normal.
The Master operation is to check whether the host name associated with the IP address in the hosts file is the same as the host name in the hostname.qfe1 file. If no, the named process cannot be started. The contents in the Hosts file are as follows: 127.0.0.1 localhost 10.238.46.228 XJDNS01BHW.XJ.GPRS.Chinamobile.com 10.238.46.214 DNSMASTER_MAINTAIN The contents in the Hostname.qfe1 file are as follows: XJDNS01BHW.XJ.GPRS.Chinamobile.com The configuration information in these files is correct. - Check the configuration of the named.conf file.
Run the following command: /usr/local/sbin/named-checkconf /etc/named.conf You can find that the named.conf file is normal. - Check whether every zone file is normal.
- Check the named.cache file.
Run /usr/local/sbin/named-checkzone /var/named/named.cache. An error message is returned. You can find an additional semicolon (;) on the last line of the file. Delete the semicolon from the named.cache file and restart the named process | 
Favorite (0)
Reply
