For years we've just had the one server (now several), and each server had its format for single-server nameservers:
servername1.mydomain.com
servername2.mydomain.com
Now with multiple servers, and confused clients, we're wanting to setup clustered DNS. A single list of nameservers that any hosting server can make use of, and for better redundancy within our infrastructure.
My primary question is how we roll it out to customers. I already know pretty well how to set it up, link them to various hosting servers, etc. What I don't know is how this will impact clients.
We're still in the planning phase of this, but want to move quickly. Just looking to square away a couple of those important items. Many customers control their own domain name, and some don't even know their current password I'm sure, so I'm trying to anticipate some of the issues we'll run into.
It would be great if we can somehow do a slow rollout, where early adopters can jump onboard when they want to the new DNS servers, and we can continue to transition others over time as communication between us and the client allows.
Thanks for your help. Should be an interesting thread!
servername1.mydomain.com
servername2.mydomain.com
Now with multiple servers, and confused clients, we're wanting to setup clustered DNS. A single list of nameservers that any hosting server can make use of, and for better redundancy within our infrastructure.
My primary question is how we roll it out to customers. I already know pretty well how to set it up, link them to various hosting servers, etc. What I don't know is how this will impact clients.
- Can we have some clients on the new NS servers, and others on the old ones?
- What happens if some clients are slow to respond to our request to update nameservers?
- Do we need to plan for a cutover window?
- Are there any conflicts I need to know about, such as the same DNS zone being present on more than one server?
We're still in the planning phase of this, but want to move quickly. Just looking to square away a couple of those important items. Many customers control their own domain name, and some don't even know their current password I'm sure, so I'm trying to anticipate some of the issues we'll run into.
It would be great if we can somehow do a slow rollout, where early adopters can jump onboard when they want to the new DNS servers, and we can continue to transition others over time as communication between us and the client allows.
Thanks for your help. Should be an interesting thread!