Results 1 to 5 of 5
  1. #1

    Question Any known problems/issues with cpanel's DNS Clustering?

    We are thinking to switch our servers to use cpanel's DNS Clustering.

    Are there any known issues or problems? Any "gotcha's" that might pop up?

    For me, the advantage to dns clustering is the "ease of use" for nameservers for our clients. Since cpanel doesn't support clustered web services (different server for mail/web/db, etc), there is little technical advantage to have dns on different servers.. since if the "main server" is dead, then having working dns is little help.

    BUT, having the ability to always have the SAME nameservers for every server, is a nice feature since most of our clients are not techy, and get confused easily when we ask them what server they are on to figure out what nameservers they "should" be using, etc. It would be nice to just always give them "ns1/ns2/ns3/ns4.ourdomain.com" and that's it.

    Thoughts?
    Want to sell domain names? Sign up today for an eNom.com reseller account from a trusted eNom ETP provider.
    * We provide support and service to over 3245 happy eNom domain name and SSL certificate resellers!

  2. #2
    Join Date
    Apr 2002
    Location
    USA
    Posts
    5,764
    How many servers?
    Drives load way high if too many severs are in the cluster when it starts the synicing of zone files.

  3. #3
    For now, only a few servers. Maximum we might have in the cpanel cluster would be 12 - 15.

    Does that sound like it would drive load too high? If so, we'd be happy to run DNS on a few isolated servers.. would that help?
    Want to sell domain names? Sign up today for an eNom.com reseller account from a trusted eNom ETP provider.
    * We provide support and service to over 3245 happy eNom domain name and SSL certificate resellers!

  4. #4
    Join Date
    May 2002
    Location
    UK
    Posts
    1,616
    Quote Originally Posted by mrzippy
    Are there any known issues or problems? Any "gotcha's" that might pop up?
    We initially looked into this a couple of years ago when cPanel first rolled it out. At that time it worked great for shared hosting but was a non starter for reseller account servers due to major insecurities related to reseller's WHM access (they had ability to wipe out any dns zone in the cluster whether they owned it or not).

    A while ago, cPanel reworked their DNS management backend and this was a major improvement fixing the problems previously mentioned. Since this time, we have been running it on both shared servers and around 30% of our reseller account servers with no issues. The plan is to intergrate our other reseller account servers soon.

    It can be a bit of a pain if you're used to manually editing DNS zones via SSH by editing /var/named/domain.com.db then "rndc reload" to bring the changes in because this no longer works when the server is in a DNS cluster. You need to either edit the zone via WHM or run a cPanel script after the manual edit to migrate the zone change to the DNS cluster (can't remember the script right now).

    I should point out that we use two independant servers for the DNS servers and do not use these boxes as regular hosting servers. I've heard some stories of problems when people have two regular hosting servers and they try to use them as a DNS cluster aswell. As for resources used on the DNS servers, we've not seen any problems here. Load is usually below 0.30 on both and they're serving around 5000 DNS zones.



    there is little technical advantage to have dns on different servers.. since if the "main server" is dead, then having working dns is little help.
    I disagree. If your main hosting server is down but the DNS zones are still online this can be the difference between email bounces (not able to lookup MX) and email queued on sending server (can lookup MX but not connect, will try later).

    Also, any customers who have their own Exchange servers or remote MX will stay online along with any subdomains pointing to a remote IP. If you have backup MX setup for your clients (which, compared with clustered DNS is easy to setup) this is pointless if your DNS is down when the server is down.


    BUT, having the ability to always have the SAME nameservers for every server, is a nice feature since most of our clients are not techy, and get confused easily when we ask them what server they are on to figure out what nameservers they "should" be using, etc. It would be nice to just always give them "ns1/ns2/ns3/ns4.ourdomain.com" and that's it.
    Yes, it's much easier to have one set of nameservers for everyone. That's a major plus. Another major plus point in this is that it allows you to spread your DNS servers out between different locations (in line with RFC's) and shows an attention to detail which, in my experience, many customers appreciate.

    HTH
    Clook Internet
    UK based web hosting, reseller accounts and fully managed dedicated and virtual servers! In our 12th year and counting...

  5. #5
    Thanks Jim, that is great info.

    Want to sell domain names? Sign up today for an eNom.com reseller account from a trusted eNom ETP provider.
    * We provide support and service to over 3245 happy eNom domain name and SSL certificate resellers!

  6. Newsletters

    Subscribe Now & Get The WHT Quick Start Guide!

Related Posts from theWHIR.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •