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
- Ensure GoDaddy A records point to 75.2.70.75 and 99.83.190.102, with a CNAME set to proxy-ssl.webflow.com, and remove conflicting DNS records.
- Verify Webflow settings under Project Settings > Hosting, ensuring the WWW version is the default domain.
- Flush local DNS cache (
ipconfig /flushdnson Windows,sudo dscacheutil -flushcacheon macOS) and check DNS records using whatsmydns.net. - Remove any unintended 301 redirects in Webflow's Hosting settings.
- Check with GoDaddy to ensure no old forwarding settings remain from previous hosting.
- Allow up to 48 hours for DNS propagation and test in incognito mode or a different browser.
It sounds like your domain is still redirecting to another site even after updating the A records and CNAME in GoDaddy. This is likely due to DNS caching, old redirects, or incorrect settings. Follow these steps to troubleshoot.
1. Check Your DNS Settings in GoDaddy
- A Records: Ensure you have only the required Webflow A records:
- 75.2.70.75
- 99.83.190.102
- CNAME Record: There should be a CNAME pointing to proxy-ssl.webflow.com (for www domain).
- Delete Any Extra Records: Remove any conflicting A, AAAA, or CNAME records that could be redirecting traffic elsewhere.
2. Verify Webflow’s Domain Settings
- Go to Webflow > Project Settings > Hosting.
- Check the “Custom Domains” section: It should show your domain correctly, with no errors.
- Ensure the WWW version is set as the default domain. Webflow recommends using www as primary.
3. Clear DNS Cache and Test
- Flush Local DNS Cache:
- On Windows: Open Command Prompt and run:
ipconfig /flushdns - On macOS: Open Terminal and run:
sudo dscacheutil -flushcache - Use an External DNS Checker:
- Check your updated DNS records at tools like https://www.whatsmydns.net/.
- Ensure both A records and CNAME are pointing to Webflow.
4. Look for Redirects in Webflow
- Go to Webflow > Project Settings > Hosting > 301 Redirects.
- Remove any unintended redirects that might be sending visitors to a different domain.
5. Check for Previous Hosting's Redirects
- If your domain was previously hosted elsewhere (e.g., another provider), there might be an old redirect still active.
- Contact GoDaddy support to ensure no forwarding settings exist on their end.
6. Wait for Full Propagation
- DNS changes can take up to 48 hours to fully propagate.
- Test using Incognito Mode or a different browser to avoid cached results.
Summary
Fixing this issue involves checking DNS settings, clearing caches, confirming Webflow settings, and removing any unwanted redirects. If the problem persists after 48 hours, contact GoDaddy support to ensure no hidden forwarding rules exist.