Assigning new site DNS to existing domain


#1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My current domain is: https://kiewacatchmentlandcare.org.au with certbot installed
The new site we have been developing is at https://159.65.129.176 which currently gives “This site is not secure” warning which we ignore during development
But we are ready to publish the new site which means pointing the existing domain name to the new ip address 159…
Just wondering how will Certbot respond to the new dns settings? and can i anticipate problems?

My web server is (include version): a VPS on DigitalOcean

The operating system my web server runs on is (include version):Ubuntu 16.04

My hosting provider, if applicable, is: Digital Ocean

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m not using a cpanel to manage my site just using DO tools and the command line
regards
swampy


#2

The Let’s Encrypt validation servers react to DNS changes very quickly. You should be able to issue a new certificate right away as soon as the changes appear on your authoritative DNS server.

There will be a brief window where visitors to your website get security errors. If you want to avoid any downtime at all, you could copy your old certificate to the new server and configure it before cutting it over.


#3

Patches
Thanks for the 100% accurate (as it turned out) reply anticipating how my new system would respond to the change of IP - it was a painless process! and not requiring the copy of the old certificate to the new server
Your assistance was much appreciated


#4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.