Named Server broken after recent automatic update - how did this happen?
Posted: Thu Nov 15, 2018 12:17 am
My VestaCP DNS Named Server of one of my VPSs got completely corrupted after the recent automatic update. I have two VPSs at two different hosts. With the one there was also a problem with DNS after the update, but I was able to work my way out of the problem just by restarting VestaCP and resaving the DNS. With the second VPS I couldn't fix it as the configuration for the named server host got completely corrupted. The host domain was dead.
First sign was that although the IP worked, the domain was not pointing at the IP any longer. With the first VPS the primary domain worked when I used the IP. But with the second VPS the primary domain DNS was completely corrupted. In both cases the ioncube was also disabled. All of this happened immediately after the last update. I'm on automatic updates.
With the second "corrupted" DNS VPS I first tried to restart the Named Server in the VestaCP Server section, that didn't work.
I then followed the steps that Skurudo suggested in a previous thread but that didn't work either:
viewtopic.php?t=8471
This is really scary. How did this happen? What was in the recent update that affected my DNS Named Server? What does one do when that happens to the VPS?
First sign was that although the IP worked, the domain was not pointing at the IP any longer. With the first VPS the primary domain worked when I used the IP. But with the second VPS the primary domain DNS was completely corrupted. In both cases the ioncube was also disabled. All of this happened immediately after the last update. I'm on automatic updates.
With the second "corrupted" DNS VPS I first tried to restart the Named Server in the VestaCP Server section, that didn't work.
I then followed the steps that Skurudo suggested in a previous thread but that didn't work either:
viewtopic.php?t=8471
Looks as though with the last update the configuration for the host domain of the second VPS got completely corrupted. In the end the only solution left for me was to uninstall VestaCP and reinstall VestaCP from scratch. That took loads of time to do.chown root:named /etc/rndc.key
chmod 640 /etc/rndc.key
service named restart
This is really scary. How did this happen? What was in the recent update that affected my DNS Named Server? What does one do when that happens to the VPS?