Hi.
I got a fresh install of Sentora. Added a client, logged in as client, added my domain.
Pressed "Create records".
The /etc/sentora/configs/bind/zones does not contain my domain.
The /etc/sentora/configs/bind/etc/named.conf does not contain anything.
The logs does not say something about this, and the DNS manager says everything is OK.
Running CentOS6 with MySQL server 5.6
Some help maybe?
Lots of stuff in Sentora is done by the daemon which is running (i think) every 5 minutes.
Have you waited for the daemon or started it manually?
You can run it manually if you're impatient like me
Code:
sudo /usr/bin/php -q /etc/sentora/panel/bin/daemon.php
I did try that, happened nothing to the DNS.
I tried one more thing; When I first pressed "Create DNS records", and then try to add a new record, I get error 500. This happens in this:
http://server01.domain.tld/?module=dns_m...on=SaveDNS
And I guess it is the file /etc/sentora/panel/modules/dns_manager/code/controller.ext.php that is a problem.
I tried to run it manually from the console, I did run
"php /etc/sentora/panel/modules/dns_manager/code/controller.ext.php"
And the otput were:
PHP Fatal error: Class 'ctrl_module' not found in /etc/sentora/panel/modules/dns_manager/code/controller.ext.php on line 30
...?
have you edited something or changed the file permissions?
No. Not at all.
What should they be?
Hey!
I solved this issue by watching all the output from the installer. I found some errors where is not covered by installer.
I did reinstall the VPS to Ubuntu 14.04 minimal, and had to do this before I did run the install script:
apt-get install cron e2fsprogs curl dialog -y
Then
apt-get --reinstall install bsdutils
Then run the install script.
Everything works now
I got one more issue after this, I don't know if this applies to every installation, or is just unique for me, but;
I checked the "Service status" page, and did see that port 53 was closed. It looked like bind9 was ***** up and didn't run, so I just backed up named.conf and reinstalled bind9, then restored named.conf. Now everything works!
One more thing that is missing in this CP;
When you edit DNS-zones in the control panel, you must restart bind9 to make the changes take effect.
I solved this by setting bind9 restart in a cronjob.