Our main website was moved to a new webhost and a new domain. We control our DNS and were instructed to change the A record for olddomain.com to point it to the new host newdomain.ca.
We lowered the TTL about a week before the change and made the change on November 1st.
Since then some, not all, clients e.g. mobile and desktop of varying browsers are getting certificate errors when browsing to https://olddomain.com. If the option is available to continue anyway then you are sent to https://newdomain.ca and the correct cert shows.
We were told that this issue with with the local clients that had previously browsed to the website and are caching the old certificate for olddomain.com. Further to that the easiest thing to do would be to migrate DNS to new nameservers so that local clients would be forced to purge the old cert.
That's almost makes sense to me except I don't understand why the issue persists if I clear my SSL state and browser cache.
Why I am still getting certificate errors when browsing to https://olddomain.com? It should just be redirecting to newdomain.ca
0 Answers