Splitting the DNS

M

MtK

Verified User
Joined
Aug 2, 2007
Messages
405
Hey,
I have several DA installations with 100s of domains on each of them.
2 of these machines also act as the DNS of all the rest (using the multi-server feature).

should I consider splitting the DNS service into a separate machine?
i.e a DA installation having only the NAMED service ON.
 
Well you can make that work in a single box without point your ns1/ns2 IP to that... and check with dig if everything is working, once done, you may want to switch in production.

Many users now use that software and is pretty stable.

For split what you mean? Have some domain on one server some other on another one? What the sense of that? Take two little server (i do use two dell server with single Pentium 4 CPU) and use just for DNS with DirectSlave

Regards
 
SeLLeRoNe said:
For split what you mean? Have some domain on one server some other on another one? What the sense of that? Take two little server (i do use two dell server with single Pentium 4 CPU) and use just for DNS with DirectSlave
Click to expand...
By split I mean, the server now is used for both HTTP and DNS services.
after split I'd have 1 server for HTTP and another for DNS.


SeLLeRoNe said:
Take two little server (i do use two dell server with single Pentium 4 CPU) and use just for DNS with DirectSlave
Click to expand...
How much RAM you have on them?
And how many Clients/Domains does that serve?
 
Last edited:
It does have 4GB Ram, for now serve about 300 domain, but, probably will be able to manage about 5000 or more, DNS service is not that "heavy" for a server to manage.

So, for split you mena what is the common use of DNS separated from other services, so, check DirectSlave and build a little box just for that (or a small VPS).

Regards
 
DNS is not very resource hungry; we have multiple slave nameservers on relatively small virtual severs. Hosting DNS for thousands of domains, without issues. Of course it does depend to some extend how many hits your DNS servers are getting, but with the default TTL, it shouldn't be a big load. We don't even see a big load with a TTL of 600.

Jeff
 
As it was already mentioned, moving DNS to a self-standing server is reasonable in two cases (at least how I see it):

1. If DNS service and DNS queries affect the server and make the HTTP service to respond slowly.

2. Or if you need to host DNS servers in different DC or countries.

We have the both variants, when DNS servers are located in other DC (i.e. moved from Directadmin powered servers), and when DNS services are co-hosted with HTTP/MAIL services on Directadmin servers as well. So it mostly depends on your personal preferences.
 
You must log in or register to reply here.
Back
Top