Good morning.
My client received the attached notice. I’ve also attached a screenshot of his DNS A records. ChatGPT says the A records are not correct. Does anyone know what I need to do to fix this?
Thanks!
Good morning.
My client received the attached notice. I’ve also attached a screenshot of his DNS A records. ChatGPT says the A records are not correct. Does anyone know what I need to do to fix this?
Thanks!
Hi there,
Following our DNS record migration from April 9, 2025, you’ll need to update your DNS configuration. Please check your records in Site settings > Publishing > Production.
For A records, use one of these configurations:
Important: Remove any additional A records to prevent conflicts with Webflow’s DNS configuration. After updating the records, verify the connection by clicking “Check status” under your domain name.
Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.
Obviously AI is not reading the screenshot. Does this mean that I need to delete all other A records except for the two at the top?
Thanks,
Mark
No those A’s are fine, look in the left column you can see they are for different subdomains.
You only care about the base ( blank or @ ) record and the www record.
If I do a quick cert check online, the expiry date shows as 08-Oct, while the date your email shows is August.
My guess is your client previously had the site hosted on a cpanel-type server, and never really shut that down. They might even still be paying for those hosting services including SSL.
The only one you probably need to think about is email, I usually migrate customers to Google Workspace.
Michael, you’re right. The Inmotion host is still active. I contacted them and they said the DNS is currently managed by them. If I cancel the hosting plan, an active hosting account is required for DNS management. They recommended using Cloudflare. They said I can get a free account at Cloudflare, re-add all the necessary DNS records, (I should be able to scan for the existing ones: https://developers.cloudflare.com/dns/zone-setups/reference/dns-quick-scan/), and then update the nameservers by following this guide: https://www.inmotionhosting.com/support/domain-names/change-domain-nameservers-amp/.
Do you think this is the best way to go?
Thanks,
Mark
Yep, Cloudflare is my preferred DNS.
Again double check email before you shut down the old hosting.
Michael,
I’ve created a free account on Cloudflare for my client and did a scan and it found the records shown on the screenshot. It recommended putting an A or CNAME record with www but I see that there is a CNAME with www.
If I click on Continue to activation, will Cloudflare then take care of the hosting? Can I then delete the hosting from the Inmotion host? Also, are all the records shown on this screenshot to be left alone?
By the way his email is not hosted at Inmotion. He has a Gmail email.
Thanks,
Mark
Did you watch my vid?
Make sure to switch OFF the orange proxy switch.
An @gmail.com email? If so then you don’t need those MX records. NS records can be removed also, if they are deleteable. Most the the others are not relevant either unless you’re still using other services.
Once you update the nameservers at your registrar and Cloudflare is properly connected, sounds like you can cancel the old hosting services. Sounds like your client just wants the Webflow site and their @gmail.com email, so all good.
Michael,
Didn’t realize there was a vdeo to watch. Just did watch it and turned off the orange proxy switches.
Everything is working just fine.
Thanks,
Mark
To switch off the Orange proxy switch enables, or rather disables, Cloudflare’s security Priority Codes. Now, I don’t know about you, but if you were to look at the screenshot attached, I’m pretty certain that Webflow doesn’t have anywhere near the ability or capacity to solve the kind of attacks that websites such as ours have. Hence why we use a reverse proxy.
However, the most recent changes by Webflow appear to have completely rendered the SSL certificate in a terrible space. Moreover…