Common issues
This article provides solutions to the most common issues you may have when using ISPmanager Business.
Issues with DNS-server
PowerDNS logs and files
PowerDNS configuration file
CentOS: /etc/pdns/pdns.conf
Debian: /etc/powerdns/pdns.conf
PowerDNS domain records
The records are kept in MySQL databases, a separate base for every name space. The default name space is powerdns for CentOS, pdns for Debian.
PowerDNS logs
CentOS: /var/log/messages
Debian: /var/log/syslog
Master DNS-server diagnostics
DNS server does not respond to request for domain zone
Make sure the DNS-server on the master server responds to requests for the domain zone:
dig <domain> @<IP address> ANY +short
The response will look something like this:
dig domain.name @1.1.1.1 ANY +short
mary.me. root.example.com. 2014041800 10800 3600 604800 86400
ns2.example.com.
ns1.example.com.
"v=spf1 ip4:1.1.1.1 a mx ~all"
10 mail.domain.name.
1.1.1.1
The following response indicates that the DNS-server is not running:
dig domain.nam @1.1.1.1 ANY +short
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> domain.nam @1.1.1.1 ANY +short
;; global options: +cmd
;; connection timed out; no servers could be reached
An empty response indicates that the DNS-server doesn't have information about the domain. Perhaps, it could not upload the domain zone. Open the log for more details.
Slave name server diagnostics
Checking connection with the DNS-server
Try to connect to port 53 of the master server through telnet:
telnet <IP address of the master server> 53
If you cannot connect, check the Firewall settings on the master and slave servers.
Checking domain zone transfer from the master to the slave server
Execute the command:
dig <domain> @<IP-address> axfr
The response should look like this:
dig domain.name @1.1.1.1 axfr
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> domain.name @1.1.1.1 axfr
;; global options: +cmd
domain.name. 3600 IN SOA mary.me. root.example.com. 2014041800 10800 3600 604800 86400
domain.name. 3600 IN NS ns1.example.com.
domain.name. 3600 IN NS ns2.example.com.
domain.name. 3600 IN TXT "v=spf1 ip4:1.1.1.1 a mx ~all"
domain.name. 3600 IN MX 10 mail.domain.name.
domain.name. 3600 IN A 1.1.1.1
ftp.domain.name. 3600 IN A 1.1.1.1
mail.domain.name. 3600 IN A 1.1.1.1
pop.domain.name. 3600 IN A 1.1.1.1
smtp.domain.name. 3600 IN A 1.1.1.1
www.domain.name. 3600 IN A 1.1.1.1
domain.name. 3600 IN SOA mary.me. root.example.com. 2014041800 10800 3600 604800 86400
Issues with web-server
Web-server files
Apache configuration file
CentOS: /etc/httpd/conf/httpd.conf
Debian: /etc/apache2/apache2.conf
Nginx configuration
CentOS, Debian: /etc/nginx/nginx.conf
Issues with website statistics collection
Statistics is not displayed to a user
Statistics for a WWW-domain is stored in /var/www//data/www//webstat. Make sure that the files in this directory belongs to the user.
Statistics displays only one unique visitor
This problem can occur if both Nginx and Apache are installed. To resolve the issue, install mod_rpaf for Apache.
Zero statistics
Check that the AWStats configuration file for the WWW-domain /etc/awstats/awstats..conf) has the parameter:
Awstats configuration file
LogFormat=1
Check the Apache configuration file for the WWW-domain /conf/vhosts// contains the forward — "combined":
Apache configuration file
CustomLog /var/www/httpd-logs/<WWW-домен>.access.log combined
How to exclude my IP from statistics
Add the following string into the configuration file /etc/awstats/awstats..conf.
Awstats configuration file
SkipHosts="<IP address>"