Why is my website still getting redirected to a different domain after transferring to Godaddy and setting up A records and a CNAME as instructed by Webflow?
TL;DR
- Confirm correct default domain and hosting settings in Webflow, ensuring SSL and redirect options are properly configured.
- Verify GoDaddy DNS records match Webflow's requirements and remove any old A/CNAME records or URL forwarding.
- Clear browser cache, allow 24–48 hours for DNS propagation, and confirm global DNS status with tools like whatsmydns.net.
Your site is likely still redirecting because of residual DNS configurations, improper domain settings in Webflow, or HTTP redirect settings persisting from the previous setup.
1. Verify Domain Settings in Webflow
- Go to Project Settings > Hosting tab in your Webflow dashboard.
- Under the Custom Domains section, confirm that only the domain(s) you want are listed (e.g., yourdomain.com and www.yourdomain.com).
- Make sure the correct default domain is selected (usually the www version). The default domain is where all other versions are redirected.
2. Check A Records and CNAME in GoDaddy
- Your domain should have two A records pointing to Webflow’s servers:
- (a) 75.2.70.75
- (b) 99.83.190.102
- You should have one CNAME record:
- Host: www
- Points to: proxy-ssl.webflow.com
- Remove any old A records or CNAMEs that don’t match the above.
3. Remove Old Redirects or Forwarding
- Log into your GoDaddy dashboard and check for any URL forwarding or domain forwarding set up under Domain Settings or Forwarding.
- If forwarding is active (e.g., www.yourdomain.com → otherdomain.com), disable or delete it.
4. SSL and Redirect Settings in Webflow
- In Webflow Hosting settings, confirm that the SSL is enabled.
- Ensure “Force SSL” and “WWW or root domain redirect” are configured correctly. If you're using www as the primary domain, Webflow should redirect non-www to www.
- Make sure there’s no custom code in the Webflow project (under Page Settings > Custom Code) that includes a forced redirect.
5. DNS Propagation and Browser Cache
- Changes can take time to propagate. Allow up to 24–48 hours after updating DNS records.
- Clear your browser cache or test using an incognito window.
- Use a tool like whatsmydns.net to check if the correct DNS records are propagating globally.
Summary
Check that your Webflow hosting settings point to the correct default domain, ensure the DNS setup in GoDaddy matches Webflow’s required A records and CNAME, remove any domain forwarding in GoDaddy, and verify there are no custom redirects or leftover configuration causing the redirection.