Skip to main content

Weird DNS cluster behavior

schrill9
Hi there. To explain my issue in short. I have a 4 cpanel ex. A,B,C and D. Which are DNS clustered in such way. A -->D, B-->D, C-->D in instances A,B and C's DNS cluster configuration for instance D is set to synchronize (server D is running DNS cpanel only) in server D's DNS cluster configuration all 4 servers A,B and C are set to standalone. My problem arose after upgrading to cloudlinux and follows. When an new account ex.testing is created on either A,B or C and if the same account ex.testing is present on the other servers every other server gets it's own zone record overwritten for that account ex. testing from the newly created account ex.testing on server one (note. they are not clustered to each other only to server D) the record gets overwritten but the changes are not made valid (only by zone edit in WHM can one see that all servers have identical zone configuration for domain ex.testing.com) if dig is used the old parameters are still valid (only for the other servers, not the server where the account was not present and newly created) not until a manual change to any of the zone records on the affected servers is made thus making the new settings valid and visible with dig (change has to be made manually on each server except the first where the account was newly created). If that account ex.testing is deleted on any of the other servers where it resides and by a chance that account is present on the other servers the zone record for that account is deleted from all servers (configuration in zone edit under whm is visible, but dig returns null) This behavior resulted after all servers were upgraded to v.58 and cloudlinux was installed on them. ps. no server cluster is set only DNS cluster and in the described manner which before the upgrade resulted in one way sync from A,B and C to D, not in betwean. Steps to reproduce: Cluster DNS servers as such A-->D B-->D C-->D. Server D gets synchronize parameter under DNS cluster configuration on servers A,B and C Servers A, B and C get standalone parameter under DNS cluster configuration on server D Create account on server A ex.testing domain ex.testing.com Create account on server B ex.testing domain ex.testing.com Create account on server C ex.testing domain ex.testing.com Delete account on server B ex.testing domain ex.testing.com All server info /etc/redhat-release:CloudLinux Server release 6.8 (Oleg Makarov) /usr/local/cpanel/version:11.58.0.24 /var/cpanel/envtype:kvm CPANEL=release Server version: Apache/2.4.23 (Unix) Server built: Aug 24 2016 14:13:42 Cpanel::Easy::Apache v3.34.4 rev9999 +cloudlinux PHP 5.6.25 (cli) (built: Aug 24 2016 14:20:26) Copyright (c) 1997-2016 The PHP Group Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies with the ionCube PHP Loader v4.7.5, Copyright (c) 2002-2014, by ionCube Ltd., and with Zend Guard Loader v3.3, Copyright (c) 1998-2014, by Zend Technologies mysql Ver 14.14 Distrib 5.5.50, for Linux (x86_64) using readline 5.1

Comments

3 comments

Date Votes
  • cPanelMichael
    Steps to reproduce: Cluster DNS servers as such A-->D B-->D C-->D. Server D gets synchronize parameter under DNS cluster configuration on servers A,B and C Servers A, B and C get standalone parameter under DNS cluster configuration on server D Create account on server A ex.testing domain ex.testing.com Create account on server B ex.testing domain ex.testing.com Create account on server C ex.testing domain ex.testing.com Delete account on server B ex.testing domain ex.testing.com

    Hello, The "Keep DNS Zone" option is available when terminating an account if you want to preserve the DNS zone across other servers in the cluster. It's documented at:
    0
  • schrill9
    Hello, The "Keep DNS Zone" option is available when terminating an account if you want to preserve the DNS zone across other servers in the cluster. It's documented at: Terminate an Account - Documentation - cPanel Documentation Could you let us know if this is what you were looking for? Thank you.

    My question was probably is this intended behavior? Will servers if not directly linked in the cluster still be linked through a third server as in my case and thus exhibit the above behavior? I've also tried write only option on all servers (except server D) and I get an error saying it cannot create the db file
    Hello, The "Keep DNS Zone" option is available when terminating an account if you want to preserve the DNS zone across other servers in the cluster. It's documented at: Terminate an Account - Documentation - cPanel Documentation Could you let us know if this is what you were looking for? Thank you.

    Hello, The "Keep DNS Zone" option is available when terminating an account if you want to preserve the DNS zone across other servers in the cluster. It's documented at: Terminate an Account - Documentation - cPanel Documentation Could you let us know if this is what you were looking for? Thank you.

    Hi there, tnx on the fast response! My question was, is this expected behavior as in the case above when servers are not linked to each other on the cluster but through a third server?
    0
  • cPanelMichael
    My question was, is this expected behavior as in the case above when servers are not linked to each other on the cluster but through a third server?

    Yes, this is by design. I believe the feature you are seeking is discussed at: Ownership and access control of zones in the dns server. Thank you.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post