BlueNoteWeb
Verified User
This question isn't specific to DirectAdmin, but hopefully someone here can help out.
Currently we have a couple of shared servers for clients, one running DA and another running cPanel. At my registrar I have ns1 and ns2 for my main domain pointing to the DA box, ns3 and ns4 pointing to the cPanel box. Clients are told when they sign up whether to use 1 and 2 or 3 and 4 depending on if they choose DA or cPanel.
So now we're looking at expanding to a third server. I could set up ns5 and ns6...but that gets crazy especially when we look at 4 servers, or 5, or 6 or....
I'm thinking I could set up two small servers (probably even on VPS for now), in two different datacenters, call them ns1 and ns2. Set up named on each, add a cronjob that rsyncs all of the named files from each server every so often (4 hours?), and tell all new clients to use ns1 and ns2. I could point ns3 to one and ns4 to the other for backwards compatibility.
That gives me DNS hosted in two different physical locations, providing some redundancy, and I don't have to concern myself with which nameservers new clients should use (since it's ALWAYS ns1 and ns2). We can manage DNS changes through the normal methods in the respective control panels, clients who have access to their own DNS manage it just as they do now. DNS changes would be delayed slightly, but it's no big deal to log in and manually do an rsync if it's needed.
Does that all make sense to do? Is there a better way to do this? Am I reinventing the wheel here?
Currently we have a couple of shared servers for clients, one running DA and another running cPanel. At my registrar I have ns1 and ns2 for my main domain pointing to the DA box, ns3 and ns4 pointing to the cPanel box. Clients are told when they sign up whether to use 1 and 2 or 3 and 4 depending on if they choose DA or cPanel.
So now we're looking at expanding to a third server. I could set up ns5 and ns6...but that gets crazy especially when we look at 4 servers, or 5, or 6 or....
I'm thinking I could set up two small servers (probably even on VPS for now), in two different datacenters, call them ns1 and ns2. Set up named on each, add a cronjob that rsyncs all of the named files from each server every so often (4 hours?), and tell all new clients to use ns1 and ns2. I could point ns3 to one and ns4 to the other for backwards compatibility.
That gives me DNS hosted in two different physical locations, providing some redundancy, and I don't have to concern myself with which nameservers new clients should use (since it's ALWAYS ns1 and ns2). We can manage DNS changes through the normal methods in the respective control panels, clients who have access to their own DNS manage it just as they do now. DNS changes would be delayed slightly, but it's no big deal to log in and manually do an rsync if it's needed.
Does that all make sense to do? Is there a better way to do this? Am I reinventing the wheel here?
.