The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Dns Clustering

Discussion in 'Bind / DNS / Nameserver Issues' started by r00t316, Apr 28, 2004.

  1. r00t316

    r00t316 Active Member

    Joined:
    Nov 29, 2003
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    6
    Well I know many people would like a simple answer to cpanels / whm dns clustering.
    However it has some flaws which if you are not an experienced admin it could create havok on your name servers.
    Exspecially if you were to say transfer clients from 1 machine to another.

    So I figured what the heck why not figure out a way which would do the clustering but not cause all the problems?

    I created my own clustering which will work for the time being.
    However hopefully the dev team here will maybe implement this into one of the next releases of whm.

    We have 2 name servers.
    ns1.whatever.com.
    ns2.whatever.com.

    We have 4 web servers
    web1
    web2
    web3
    web4

    How it should work in theory.

    web1 should only have zone files which are hosted on web1 only
    web2 should only have zone files which are hosted on web2 only
    web3 should only have zone files which are hosted on web3 only
    web4 should only have zone files which are hosted on web4 only

    Which I thought this was the case but it isn't.

    I want to add clustering
    I setup the clustering and add ns1.whatever.com and ns2.whatever.com to web1's dns clustering.
    Presto instant clustering of zone files for web1 only.
    Any changes made on web1 zones will be updated to both name servers ONLY.

    same with web2 and web3 and web4

    Why does it need to put zone files for web1 on web2,web3,web4 ?
    That creates 1) A very resource intensive process on the name servers and on the web server.

    Why should it be done this way?
    web2 goes down for who knows why.
    Then it syncs its domain records.
    Well if someone adds a weird serial it seems to load the zone you don't want.
    So for example i changed bunch of domains on web1 and then web2 comes back up syncs the weird zone serials.
    web2 will overwrite the changes and you end up with old zone files again.
    This happened to us when we had to move customers to a knew server.

    So basically the jist of it is just sync the servers to the name servers.

    Now people will say "then I can not modify all the domains via the name server itself"

    You could probably do some kind of checking I would imagine or when clustering is enabled it makes directories which stores the zones in by the ip.
    /var/named/IPOFWEB1
    then it knows to update web1 if any change is made to that zone on the primary or secondary name server.



    Comments, questions, feedback
     
  2. r00t316

    r00t316 Active Member

    Joined:
    Nov 29, 2003
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    6
    noone on here has anything to say about this??
    odd.
     
Loading...

Share This Page