Hal
08-26-2006, 02:55 PM
Greetings,
There is a problem with how cPanel is updating CentOS to the newly released version (Update 8) that has just come out. cPanel is not updating bind-libs to the latest version and this is causing bind (named) to fail. If you are using your server to resolve your domain names (i.e. running name servers on it), this will cause your sites to go offline as the server is no longer resolving them. If you are also using your name server IPs for your server's resolvers, this will cause additional problems because your server will not be able to resolve any other domain names as well.
If you are experiencing this issue, here are the steps needed to take to resolve the problem:
1) Make sure your resolvers have at least two external name servers:
From the shell:
If /etc/resolv.conf only has your two name server IPs in them, please add the following two entries to the bottom of the file:
nameserver 216.86.153.14
nameserver 208.100.15.14
From WHM/cPanel:
Click on the link "Resolver Configuration" and you can replace your current IPs with the ones above.
2) Update the bind-libs RPM to the latest version:
From the shell:
type 'yum update bind-libs'
From WHM/cPanel:
Click on the "Install a RPM" link under the Software category and select the bind-libs (reinstall) package.
This will update the bind-utils to the latest version and your VPS will start to work again.
3) You can now restart named (bind)
From the shell:
service named restart
From WHM/cPanel:
click on "DNS Server (BIND)" under Restart Services
That should take care of the problem.
Note: If you're unable to access WHM due to the hostname not working, please use your IP address (i.e. http://IP:2087) to access WHM.
Feel free to contact us at support@netwisp.com if you need further help with this issue.
Hal Bouma
Netwisp, Inc.
There is a problem with how cPanel is updating CentOS to the newly released version (Update 8) that has just come out. cPanel is not updating bind-libs to the latest version and this is causing bind (named) to fail. If you are using your server to resolve your domain names (i.e. running name servers on it), this will cause your sites to go offline as the server is no longer resolving them. If you are also using your name server IPs for your server's resolvers, this will cause additional problems because your server will not be able to resolve any other domain names as well.
If you are experiencing this issue, here are the steps needed to take to resolve the problem:
1) Make sure your resolvers have at least two external name servers:
From the shell:
If /etc/resolv.conf only has your two name server IPs in them, please add the following two entries to the bottom of the file:
nameserver 216.86.153.14
nameserver 208.100.15.14
From WHM/cPanel:
Click on the link "Resolver Configuration" and you can replace your current IPs with the ones above.
2) Update the bind-libs RPM to the latest version:
From the shell:
type 'yum update bind-libs'
From WHM/cPanel:
Click on the "Install a RPM" link under the Software category and select the bind-libs (reinstall) package.
This will update the bind-utils to the latest version and your VPS will start to work again.
3) You can now restart named (bind)
From the shell:
service named restart
From WHM/cPanel:
click on "DNS Server (BIND)" under Restart Services
That should take care of the problem.
Note: If you're unable to access WHM due to the hostname not working, please use your IP address (i.e. http://IP:2087) to access WHM.
Feel free to contact us at support@netwisp.com if you need further help with this issue.
Hal Bouma
Netwisp, Inc.