Dotable - Dot your Domains - View Single Post - [Completed] Jupiter migration to new cabinet

hal · 14th July 2008, 07:53 PM

Hi Bob

it is understandable that planned downtime is necessary from time to time but, with regard to the IP changes, wouldn't it surely be easier to change the configuration of the local router rather than every nameserver on the server? With the assumption that routing protocols are being used, this would be a trivial change, incurring far less margin for error than the current plan.

If you send the new nameserver IP addresses by email after the move, how will we collect them, bearing in mind that our email relies on name resolution working properly? Should we open a helpdesk ticket, as an alternative way for us to collect our new IPs?

Thanks in advance
Hal

14th July 2008, 07:53 PM	#6 (permalink)
hal Member Join Date: May 2006 Posts: 54	New IPs Hi Bob it is understandable that planned downtime is necessary from time to time but, with regard to the IP changes, wouldn't it surely be easier to change the configuration of the local router rather than every nameserver on the server? With the assumption that routing protocols are being used, this would be a trivial change, incurring far less margin for error than the current plan. If you send the new nameserver IP addresses by email after the move, how will we collect them, bearing in mind that our email relies on name resolution working properly? Should we open a helpdesk ticket, as an alternative way for us to collect our new IPs? Thanks in advance Hal