User-backups made with AdminBackup created on 1 VPS cause domain-db's errors on other (fresh) VPS

[BBM]

I have an old VPS and recently started a new VPS. Both running AlmaLinux 9.
Both have the same DA-versions, only on 1 VPS, DirectAdmin is running on a datacenter-license and on the other/newly installed VPS, DA is running on a Personal License.

I'm encountering domain-db errors with the user-backups created on the old VPS, when extracted on the new VPS.
Tried the "fix_db.sh"-script to restore the files but this didn't work.

During the extraction the following error is posted in Messages:

DNS: Unable to read main db file for domain.nl : Can't open file /var/named/domain.nl.db for reading

Merge DB File issue, restoring to xx.xx.xx.xxx (ip of new VPS): (restore to ip)

On both VPS's the Named-directory has the same permissions, but I think there are more permission issues at hand here, but I'm a bit lost where to go from here.
I would that a new DA-install on a fresh empty VPS should not have problems with permissions?

 

[Richard G]

On both VPS's the Named-directory has the same permissions,

Directory's and files also have the same owner?

Should indeed not be an issue with a fresh install indeed.

I'm encountering domain-db errors with the user-backups created

Does that also occur if you use the Admin backup/transfer option to move the domain to the new VPS and then restore via the same option?

 

[BBM]

I used the Admin-Backup-function to transfer the backup to the new server.

But... I just checked again now (this morning I didn't check further because I noticed more errors after I did the 'fix-db.sh'-script, but now I see 'some' domain dns-entries present. But only ip4 and no Dkim or ip6 entries.
So, I guess the fix-db-script must have done something, eventhough it gave errors (Need to look in the logs somewhere to find out what kind of errors again).

Now I only need to get the remaining ip6 and dkim-entries I think.