Standalone DNS Server

[eglwolf]

I have several servers running cpanel. Each with it's own dns on it. I was wondering is it better to keep it this way, or have one main DNS (only) server that runs the dns for all my servers?

If it is better to have a DNS only server, then what would be involved in converting all my serer over to something like this. I have a VPS server I could use for a DNS only server if you think it would handle the dns for a couple thousand domains.

[chirpy]

Indeed, you should never rely on having DNS just on the local server, you will lose email and it will affect things like search engine rankings and potential site visitors with any downtime that you have.

What I would suggest is that you keep the DNS running on all the servers indivdually, plus have the VPS DNS only server. Then setup DNS clustering so that all of the servers sync to the DNs only server (but not back out again to keep the actual servers discrete if that's a security concern). You would then modify on the the nameserver records on each server that you use for that server to use the IP address of the DNS only server, and then modify the name server record for each of those nameservers at the registrar for each domain to point to the new IP address. Normal DNS propagation will then take place and the switch will be made. No downtime.

[eglwolf]

Chirpy - as usual you are my hero!

I wonder, if I started doing this process slowly, would you be able to help me go through it step by step, over the forums?

[chirpy]

I'll do what I can - go ahead. As you say, start slow, do one server at a time, preferrably with the server with fewest domains if possible.

[eglwolf]

Thanks.

The first thing I will be doing is setting up the VPS server. Now I image I only need:

Latest WHM for DNS SERVERS ONLY installer:
cpanel-universal-dnsonly-install.sea (Tue Nov 1 17:36:07 2005)

I am not familar with how to install the DNS only version. I usually just use the http://layer1.cpanel.net/latest to install cpanel.

So do I need to change to just install that version. What commands do I need to run?

[eglwolf]

I figured out that to install the DNS Only version of cPanel you use the following commands once you ssh into the server:

mkdir /home/cpins
cd /home/cpins
wget http://layer1.cpanel.net/cpanel-universal-dnsonly-install.sea
sh cpanel-universal-dnsonly-install.sea

So I am doing that now.

I believe the next thing is to set up DNS clustering on the DNS VPS correct?

I logged into whm, and there are limited menu options. When I click the Configure Cluster I get a page cannot be displayed. And all the other options (that are normal for regular cpanel installs) are blank pages. So besides installing the dns server, what needs to be done to configure it so I can configure the cluster?

[chirpy]

You need to get the remote access key on the DNS only server and then add the DNS only server to the DNS cluster on the server you're trying first.

[eglwolf]

When I go to a server and try to set up the trust relationship I get this error:

There was an error while processing your request: Cpanel::Accounting returned [HTTP/1.0 900 NET OR SSL ERROR ./cgi/trustclustermaster.cgi 30105: open_tcp_connection: failed `SERVER_IP', 2087 (Connection refused) ]

[chirpy]

Make sure that you don't have an iptables firewall running on the DNS only server blocking port 2087. And check the it is bound to port 2087:

netstat -lpn

If it isn't, try resetting the WHM Certificate if that's an option on the DNS only version, otherwise restart cPanel on that server and check the /var/log/messages for stunnel errors.

[eglwolf]

I sent you a PM with the output of running that command.

[b0072k1]

see setting up a dns standalon server would it use a lot of bandwidth at all?

[chirpy]

A DNS server would normally use very little bandwidth or server performance generally. DNS is quite an efficient protocol in both speed and packet size.

[eglwolf]

Chirpy,

Did you get a chance to review my PM?

[chirpy]

I didn't actually receive one. Feel free to send it again.

[eglwolf]

I just sent it again, I think the first time it was to long, that is why it did not send.