Cory
posted this on May 17, 2011 04:43 pm
As we look ahead we see a number of reasons why we might want to change the IP address of your website. As IP 6 rolls out we have some thoughts about SEO, we might want to have redundancy not only across different servers, but servers in different locations, we might find that performance optimizations such as using a Content Deliver Network are better done with different server configurations. We don’t really know.
What we do know is that making any change is a bit of an inconvenience for our clients. Option 1 and 2 let us make changes that improve your website without bothering you. If you don’t like that, then Option 3 is still OK by us. They are functionally the same in terms of your website working.
ALL 3 are exactly the same in that you control your DNS and at any time could change you settings to point to a different server. You're in control of your domain and all other sub domains at all times.
DNS options, in the order we recommend:
For each of these steps, any left over A records pointing to 89.234.56.134 must be changed 46.137.96.191.
Below we've mapped out instructions for the most popular domain registrars. If you have any questions about these instructions or need assistance with a registrar not listed, please let us know and we'll be happy to help.


Network Solutions does not allow delegating subdomains to other nameservers. Here we will create a CNAME for www.yourwebsite.com
If you have access to Web Host Manager (WHM)

If you use your own BIND nameserver, the instructions are here : http://www.zytrax.com/books/dns/ch9/delegate.html
Again, if you have any questions about the instructions above or need assistance with a different registrar, please open up a new support ticket and we'll be happy to help.
Comments
Done
Thanks Dipam!
If you have secondary domains redirecting to your primary one, they can be updated in the same manner. Redirects will continue to work as normal.
If we go with Option 2, should we still have the A record
I am not sure I understand the last point by Gar. At this point I do not have secondary domains
I think Gar is referring to the catch-all "A" record. With GoDaddy the A record of "@" means that anything not specified (like www.domain or mail.domain or remote.domain.com or http://domain.com) goes to the IP address listed for @.
The @ sign is used on most DNS hosting providers and Matthew is correct, it is the whatever entered or catchall plus your domain. For example, someone types in ww.yourdomain.com it will still send the request to the web server. Of course, if the webserver is not listening for "ww.yoursdomain.com" then you will get an error as the host header would need to be setup for that.
Im going with option 2 - and have done www.yourwebsite.com but cannot do a CNAME for yourwebsite.com - can only be a A Record ?
@Jeremy - Correct, set the A record for yourwebsite.com to 46.137.96.191. That URL receives very little traffic compared to www.yourwebsite.com and in the event of a future IP change we can setup a reverse proxy on our end.
Sorry I was not clear, but Matthew and Cory understood and answered. I have my cname for www.yourdomain.com pointing to my a record for yourdomain.com.
yourdomain.com was pointing to 89.234.56.134
I will now have www.yourdomain.com to yourdomain.client.prontomarketing.com and the a record for yourdomain.com pointing to 46.137.96.191 ... unless someone indicates this is incorrect.
I've completed the changes using Option #2 and changed my left over A name record to 46.137.96.191
Better late than never I suppose..... Option 1 complete and A record changed. Thanks!
Thanks Jim!
We just did option 3 and changed the IP and www to NS1 and NS2
thanks