I'm currently using Google Compute to host my website.

If I change the IP address under Google Cloud DNS will that change the instance instantly?

Upgrading Instance Video: https://www.youtube.com/watch?v=-XYUeORywXU

Or will it be delayed, like with nameserver propagation?


I have created a "clone", using a Snapshot, with the new machine specifications and hard disk size I am looking for.

  • I have checked my FTP and it works - all my php files etc are there.
  • I have checked my phpmyadmin and it is working and all tables are intact.

However, when I access the ip address in my browser it does not load the page. Does this simply mean I need to update my DNS IP Address to point to the new instance? Will this switchover be instant?

I'm trying to figure out really if the DNS IP address is something I can switch at a second's notice or if I play with it I could be disrupting my pathroute for days...

  • Basically I'm looking for a clear process to upgrade my compute server without service disruption of more than 30 minutes :) Commented Jan 15, 2016 at 10:56
  • This Stack Overflow answer suggests stopping, editing the type, and restarting the instance. Will that do? It should take well under 30 minutes. Commented Jan 15, 2016 at 11:24
  • @TomBrossman is it safe to stop the instance though? I feel really worried about this whole thing because I'm a php/mysqli/css/javascript specialist and my knowledge about hosting/servers is really limited. It's scary :( Commented Jan 15, 2016 at 12:35
  • I also want to upgrade my hard disk for more capacity. Will I be able to do that as well when up upgrade by stopping? How do I do that? Commented Jan 15, 2016 at 12:40
  • Hmmm, it will let me create a clone? Is that how I upgrade (including my disk capacity)? Commented Jan 15, 2016 at 13:18

1 Answer 1


I use Route53 which is amazons version. I can relate that I have a 60 second TTL on all my zones and when I make a change, that change syncs to their dns infrastructure in about 10 seconds. All total when I change a record with them and sync its about 2 minutes.

To affect a change to a single server I would

  1. Change or ensure ttl is at 60s.
  2. Verify that change has propogated. DIG. Old TTL plus New TTL = propogation time to first tiers.
  3. Once I see that change has propogated, then I know its just 60s to a record change.
  4. Create second record set for change to be made. TTL 60s
  5. wait a min, do the switch.

This is why I leave my TTL at 60, that and Amazons managed DNS is essentially doing l3 routing based on geo and latency for me.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.