DNS Cluster for multiple cPanel servers

[diWhile1]

What is the correct way to set up DNS CLUSTER for multiple cPanel servers (srv1.domain.com,srv2.domain.com,srv3.domain.com,...), which connect two central servers DNSonly (ns1.domain.com,ns2.domain.com).
I thought about it that way, but apparently I was wrong, or not sure:

srv1.domain.com (Write-only)-> ns1.domain.com
                (Write-only)-> ns2.domain.com

srv2.domain.com (Write-only)-> ns1.domain.com
                (Write-only)-> ns2.domain.com

srv3.domain.com (Write-only)-> ns1.domain.com
                (Write-only)-> ns2.domain.com

 

[Aaron Hatton]

What is the correct way to set up DNS CLUSTER for multiple cPanel servers (srv1.domain.com,srv2.domain.com,srv3.domain.com,...), which connect two central servers DNSonly (ns1.domain.com,ns2.domain.com).
I thought about it that way, but apparently I was wrong, or not sure:

srv1.domain.com (Write-only)-> ns1.domain.com
                (Write-only)-> ns2.domain.com

srv2.domain.com (Write-only)-> ns1.domain.com
                (Write-only)-> ns2.domain.com

srv3.domain.com (Write-only)-> ns1.domain.com
                (Write-only)-> ns2.domain.com

This is the way we have it set up however we have found the following issue:

We have recently had an issue as to where if a website is hosted on one server, for example, mydomain.com is hosted on srv1.domain.com as a cPanel website hosting account.

If the client changes MX Records from mail.mydomain.com to mail2.mydomain.com the changes will replicate to all slave servers within it's cluster but they may not replicate across to srv2.domain.com, when a support tech then changes an A record for the domain mydomain.com from srv2.domain.com it overwrites the MX record changes and thus causes issues.

 

[diWhile1]

Okay, so I tested it in my lab and found that it worked quite well

srv1.domain.com (Synchronize)-> ns1.domain.com
                (Synchronize)-> ns2.domain.com
srv2.domain.com (Synchronize)-> ns1.domain.com
                (Synchronize)-> ns2.domain.com
srv3.domain.com (Synchronize)-> ns1.domain.com
                (Synchronize)-> ns2.domain.com

ns1.domain.com (Standalone)-> srv1.domain.com
               (Standalone)-> srv2.domain.com
               (Standalone)-> srv3.domain.com
ns2.domain.com (Standalone)-> srv1.domain.com
               (Standalone)-> srv2.domain.com
               (Standalone)-> srv3.domain.com

Is there something I'm missing?
I would like to receive a formal reply from cPanel about it And if Aaron Hatton or anyone else would try to implement it and to share thoughts would be great.

 

[cPanelMichael]

Is there something I'm missing?
I would like to receive a formal reply from cPanel about it And if Aaron Hatton or anyone else would try to implement it and to share thoughts would be great.

Hello,

The method you are using is the recommended method of configuring your cluster. It matches the advice documented at:

Guide to DNS Cluster Configurations - cPanel Knowledge Base - cPanel Documentation

Thank you.