[Bug] Error in dns-cluster.pipe after DNS ip change (see #3802)

[campodoro74]

Describe the bug

See bug #3802 / #3803

When using the DNS cluster and I update a record on the main DNS server, the dns-cluster.pipe file at /usr/local/hestia/data/queue gets the wrong command; the last word 'domain' is not valid and thus the cluster is not updated.

/usr/local/hestia/bin/v-add-remote-dns-domain user thisisafakedomain.nl domain

Running is manually, the following error appears:
Error: domain type is invalid

Running the command without domain gives the error
Error: secondarydns.domain.nl connection failed

Tell us how to replicate the bug

1. Change DNS record
2. Wait more than 5 minutes and find the record not updating on the secondary DNS servers
3. Check contents of /usr/local/hestia/data/queue/dns-cluster.pipe
4. See error in command output

Which components are affected by this bug?

Control Panel Backend, Control Panel Command Line Interface, Control Panel Web Interface

Hestia Control Panel Version

v1.8.11

Operating system

Debian 11

Log capture

No response