Hello,
I had migrated about 6 servers from servers with Bind and Cloudlinux 6-7 to that of AlmaLinux 8.5/Cloudlinux 8.5 with PowerDNS I found that when doing so I would get these random instability occurrences such as
I took out the data as it's irrelevant, but It had to do with an Inconsistent state, now I can't be 100% sure that this is the reason but this time on the 8th server, I had NO such thing when I made sure that both servers matched to start meaning that both are BIND! the Cloudlinux is 6 to 8.5 but both are BIND and as such during the transfer of 800 accounts there was not a single incident with an inconsistent state.
Only post-migration did I go to Nameserver Selection and install PowerDNS again as the leading Nameserver.
It could have been a coincidence but seeing how the previous 6 servers always had at least 3-5 of these where we had to actually delete all the addon/subdomain links and recreate them to their folders post-migration to resolve the issue and this one had 0 incident, I am semi-wondering if its caused by inconsistency between migrations between BIND and PowerDNS for these zones for whatever reason.
It kept happening to addon-based domains and their respective links.
I have yet one more or two more servers to migrate from C6-7 to C8.5 to finish the upgrades, and should that also reveal 0 then that will be enough for me, I just thought to share that with others who might be considering large scale user migrations, out of 800-1000 you would get this for maybe a handful of accounts 3-5 accounts, just remember if it says "Sorry, An error occurred while adding DNS zone" you NEED to re-do it for the client or his site will not resolve properly, it's not a "warning" this really is an "ERROR", it should be RED ERROR for the account but it really returns YELLOW WARNING as it doesn't matter which is false, it really does matter for the client you are moving.
Just my two cents.
I had migrated about 6 servers from servers with Bind and Cloudlinux 6-7 to that of AlmaLinux 8.5/Cloudlinux 8.5 with PowerDNS I found that when doing so I would get these random instability occurrences such as
RESTORE: Account “xxx”: Warnings |
Sorry, An error occurred while adding dns zone: Could not store zonedata for xxx.com on x Could not remove xxx.com from the Bind configuration (named.conf) on x Configuration may be in an inconsistent state on x |
Sorry, An error occurred while adding dns zone: Could not store zonedata for yyy.com on x Could not remove yyy.com from the Bind configuration (named.conf) on Configuration may be in an inconsistent state on x |
I took out the data as it's irrelevant, but It had to do with an Inconsistent state, now I can't be 100% sure that this is the reason but this time on the 8th server, I had NO such thing when I made sure that both servers matched to start meaning that both are BIND! the Cloudlinux is 6 to 8.5 but both are BIND and as such during the transfer of 800 accounts there was not a single incident with an inconsistent state.
Only post-migration did I go to Nameserver Selection and install PowerDNS again as the leading Nameserver.
It could have been a coincidence but seeing how the previous 6 servers always had at least 3-5 of these where we had to actually delete all the addon/subdomain links and recreate them to their folders post-migration to resolve the issue and this one had 0 incident, I am semi-wondering if its caused by inconsistency between migrations between BIND and PowerDNS for these zones for whatever reason.
It kept happening to addon-based domains and their respective links.
I have yet one more or two more servers to migrate from C6-7 to C8.5 to finish the upgrades, and should that also reveal 0 then that will be enough for me, I just thought to share that with others who might be considering large scale user migrations, out of 800-1000 you would get this for maybe a handful of accounts 3-5 accounts, just remember if it says "Sorry, An error occurred while adding DNS zone" you NEED to re-do it for the client or his site will not resolve properly, it's not a "warning" this really is an "ERROR", it should be RED ERROR for the account but it really returns YELLOW WARNING as it doesn't matter which is false, it really does matter for the client you are moving.
Just my two cents.