If your DNS provider doesn't support A records or CNAME records, you won't be able to connect your custom domain to Webflow through standard configuration methods. However, there are a few alternative solutions.
1. Change to a Different DNS Provider
- Most flexible and reliable approach is to transfer your domain's DNS management to a provider that supports full DNS settings.
- You can keep your domain registered with your current registrar but update the nameservers to a service like:
- Cloudflare
- Google Domains (if supported in your region)
- Namecheap
- DNSimple
- Once switched, you’ll be able to add the needed A Records and CNAME values from Webflow’s hosting settings.
2. Use Domain Forwarding (Limited)
- Some providers that lack DNS record support may still offer domain forwarding or masking.
- This method can only redirect users to your Webflow subdomain (e.g., yoursite.webflow.io).
- Limitations:
- You won't get the benefits of full hosting under your custom domain.
- Forwarding typically breaks SSL (no HTTPS), affects SEO, and may look unprofessional.
- Some registrars might hide DNS record options or offer non-standard interfaces.
- Reach out to support and ask if they provide custom A or CNAME record support.
- Occasionally, their terminology might differ, or features may be accessible via advanced settings.
4. Re-register the Domain with a Supported Provider
- If your domain is critical and you cannot manage DNS elsewhere, consider transferring the domain to another registrar that supports DNS management.
- Most well-known registrars allow DNS access:
- GoDaddy
- Google Domains
- Namecheap
- Hover
- After transfer, you can freely set up Webflow’s required records.
Summary
If your DNS provider doesn’t support A records or CNAME, your best workaround is to delegate DNS to a supported provider like Cloudflare or Google Domains. Domain forwarding is a limited fallback, but won't fully integrate with Webflow’s hosting system.