Solved FQDN not working after moving from on premises to Google Cloud

[second2n0ne]

I have set the ip to dynamic and restarted all services, reset to static and restarted all services but FQDN does not update. Also getting certificate errors when accessing https on the new IP. Am I not waiting long enough for DNS to propogate?

 

[cobaltit]

Standard and Pro licenses have a 6hr TTL so probably not waiting long enough. And certificate errors when accessing via IP is expected since the certificate is issued to the FQDN and not the IP.

 

[second2n0ne]

Standard and Pro licenses have a 6hr TTL so probably not waiting long enough. And certificate errors when accessing via IP is expected since the certificate is issued to the FQDN and not the IP.

Thanks for the feedback...do I still need to keep the ip "dynamic" during this process?

 

[cobaltit]

It won't hurt. Since you already have it that way I'd just leave it until the FQDN resolves and then you can change it back to static.

 

[second2n0ne]

Awesome, thanks. I'll report back in ~6hrs lol!

 

[second2n0ne]

FQDN records eventually updated to reflect new IP. Thanks everyone!

 

[cobaltit]

Great, thanks for the update.