Dear ispCP users ;
An important bug exists in IspCP, affecting only
1.0.3 and
1.0.3-1 releases.
The bug is related to the generation of Bind's main configuration file (
named.conf). On affected systems, either upgrading the system or deleting a domain/alias results in an incorrect bind configuration file. This issue can be solved by applying the following fix:
Important note: Users of the aforementioned IspCP's affected versions are urged to apply the following fix to prevent any further problems.
Example for Debian:
1. Stop ispCP daemon:
Code:
# /etc/init.d/ispcp_daemon stop
2. Replacement of affected files:
Code:
# cd /var/www/ispcp/engine
# wget -O- 'http://www.isp-control.net/ispcp/raw-attachment/ticket/2146/FixBind9.tar.gz' | tar -xzv
Note: Here, only the following files are replaced:
-
ispcp-als-mngr
-
ispcp-dmn-mngr
-
ispcp_common_methods.pl
3. Fixing permissions
Code:
# sh /var/www/ispcp/engine/setup/set-engine-permissions.sh
4. Deleting old files:
Code:
# rm /etc/ispcp/bind/backup/named.conf.system
# rm /etc/ispcp/bind/working/named.conf
5. Reinstalling bind9:
Code:
# /etc/init.d/bind9 stop
# aptitude purge bind9
# aptitude install bind9
6. Save new named.conf:
Code:
# cp /etc/bind/named.conf /etc/ispcp/bind/backup/named.conf.system
7. Reset the working file:
Code:
# cp -f /etc/ispcp/bind/named.conf /etc/ispcp/bind/working/
8. Run ispcp-update script to rebuild production files:
Code:
# cd /var/www/ispcp/engine/setup
# perl ispcp-update
Cheers ;
Updated:
- Added forgotten file (ispcp_common_methods.pl).
- Fixed some mistakes in procedure.