If your domain provider does not support A Records or CNAME, you will need alternative methods to point your domain to Webflow.
1. Use a DNS Provider That Supports Full Record Control
- Transfer your DNS hosting to a provider that allows managing A records and CNAMEs, while keeping your domain registration with your current provider.
- Services like Cloudflare, Google Cloud DNS, or AWS Route 53 offer robust DNS management features for free or at low cost.
- After setting nameservers on your current registrar to point to the new DNS provider, you can configure the necessary Webflow A records and CNAME there.
2. Use Cloudflare as an Intermediary
- Create a Cloudflare account and add your domain.
- Once Cloudflare scans your DNS records, update your registrar’s nameservers to the ones Cloudflare provides.
- In Cloudflare’s DNS dashboard, add:
- A Records pointing to (a) 75.2.70.75 and (b) 99.83.190.102
- CNAME record for "www" pointing to your Webflow subdomain (e.g., proxy-ssl.webflow.com)
3. Use Webflow Domain Delegation (Enterprise Only)
- For Webflow Enterprise users, there's a potential for custom domain delegation, allowing advanced routing setups without traditional DNS inputs. Contact Webflow directly for access.
4. Change Domain Providers
- If all else fails, consider transferring your domain registration to a provider like Google Domains, Namecheap, or GoDaddy, which support full DNS record control.
- After the transfer, you’ll be able to configure A Records and CNAMEs to Webflow with no problem.
Summary
If your domain provider doesn’t support A Records or CNAMEs, the best workaround is to delegate your DNS to a provider like Cloudflare or transfer the domain to a better registrar. This allows you to set up the required DNS records for Webflow without switching your website platform.