It also wipes out /etc/named.conf.local. I just got done hand editing /etc/named.conf.local for 107 domains.

I updated the CP server with 3.0.5.4p8 a couple days ago but none of the other servers. Yesterday, when updating an existing DNS record, is when the .err extension appeared so I updated ISPConfig on the remaining server. I did the update to the .err DNS and it appeared to work fine.

Today, when add a new DNS record, I got the .err again. This is when I also noticed that /etc/named/conf.local was empty.

I have no idea why it was working fine under 3.0.5.4p5 and what was in the update to cause these problems.

I would also like to know to to rebuild the named.conf.local so I do not have to rebuild it by hand ... it's a pain for a 107 domains ... I checked the backup on the DNSs, but, it was empty too.

No, I did not try that earlier, but, thanks for letting me know that the function exist.

However, I just tried Resync and it wiped out /etc/named.conf.local on both DNSs and it created mostly .err zones. Thankfully, I made a copy of both: /var/named and /etc/named.conf.local before running Resync.

Something definitely got screwed up when I updated to ISPConfig 3.0.5.4p8.

Yeah, that's another issue, there aren't any error messages to go on in /var/log/messages

Click to expand...

Thats the same issue, when all zones were rejected by bind then the named.conf.local file has to be empty. The errors are in the syslog file, not messages. If you don't have any errors in both files, then use the named-checkzone script, run it against the .err file to see the exact error message why named refused the file. The fix that error by editing the zone in ispconfig and the zone will appear again as zone file and in named.conf.local.

If you have a customized zone config template in the conf-custom folder then it might be that your custm template is incompatible with the new ispconfig version. Compare your custom template with the one that ships with ispconfig to make the necessary adjustments to your file.

The DNSs are on a VPS running CentOS that was provisioned and I haven't changed any of the defaults as set by the NOC ... there is no /var/log/syslog ... there is only /var/log/message and there are named messages in it, for example:

Yeah, I wish it was that simple. Again, everything was working fine until I updated ISPConfig from P5 to P8. I have 107 zones in ISPConfig that use the Default DNS-Zone Template. Looking at the DNS-Zone Default Template in ISPConfig, it appears as:

The zone template is not used to send any data to a server, the template is only used to create a new zone when you add it the first time. If you want to know what is part of a dns zone then dont look at the template, what matters is the dns zone itself that you can see in the dns zone list in ispconfig, click on a zone and then go to the dns records tab of that zone to see all records.

The update script will then start to install incremental database updates for ISPConfig, if required.
Reconfigure Permissions in master database? (yes,no) [no]:
If this is a slave server in a multiserver setup, then choose "yes" here on at least one of the slave servers.

I have a stand-alone CP server, I have multi-mySQL servers, multi-DNS servers, multi-mail servers and multi-web servers ... are the servers other than the CP server considered the "slave" ... if so, on what "slave" do I answer "yes" to this question on?

Then you were asked if the services shall be reconfigured:
Reconfigure Services? (yes,no) [yes]:
You should choose "yes" here, only if you modified your system configuration manually, it might be better to choose no.

When adding a Zone, only the DNS Zone "tab" was used to create the Zone, however, none of the Records "tab" was getting being used. The DNS Zone "tab" is in the dns_soa table, whereas, the Records "tab" is in the dns_rr table.

Why only the DNS Zone "tab" gets used without needing mySQL services running on the DNS servers, I do not know and it makes no sense either.

Lesson learned: so the Records tab gets used along with creating /etc/named.conf.local, mySQL has to be running on the DNS servers.