Has anyone successfully used ALIAS records with ClouDNS to host a website on Webflow at the equivalent of mydomain.com? If not, what could be causing the issues with Webflow detecting the domain?

Using ALIAS records with ClouDNS to host a website on Webflow

ALIAS records, also known as ANAME records, are DNS records that allow you to point your domain apex (e.g., mydomain.com) to another hostname or IP address. This can be useful when you want to use a service like Webflow to host your website while keeping the domain registered with a different DNS provider like ClouDNS.

Webflow does not provide native support for ALIAS records. Instead, it recommends using A and CNAME records for domain setup. However, you can use ClouDNS as your DNS provider and still configure your domain to work with Webflow by following these steps:

Step 1: Set up your DNS in ClouDNS

1. Log in to your ClouDNS account.
2. Navigate to the DNS management section for your domain.
3. Add an A record for the root domain (e.g., mydomain.com) and point it to the IP address provided by Webflow. You can find this IP address in your Webflow project settings.
4. Add a CNAME record for the "www" subdomain and point it to the Webflow default subdomain (e.g., proxy-ssl.webflow.com).

Step 2: Configure your domain settings in Webflow

1. Log in to your Webflow account.
2. Open the project settings for the website you want to associate with your domain.
3. Navigate to the "Hosting" tab.
4. In the "Custom domain" section, enter your domain name (e.g., mydomain.com) and click "Save."

Step 3: Wait for DNS propagation
Once you have made the necessary changes in ClouDNS and Webflow, you will need to wait for DNS propagation. It may take some time for the changes to propagate across the internet.

Potential issues with Webflow detecting the domain
If you are experiencing issues with Webflow detecting your domain, it could be due to the following reasons:

1. Incorrect DNS configuration: Double-check that you have correctly set up the A and CNAME records as mentioned in the steps above. Any mistakes in the DNS configuration can prevent Webflow from detecting the domain.

2. Propagation delay: DNS changes can take time to propagate across the internet. It is recommended to wait for at least 24-48 hours after making DNS changes before troubleshooting further.

3. Cache-related issues: DNS caching can sometimes cause issues. Clear your browser cache or try accessing the website on a different device or network to rule out any cache-related problems.

4. Webflow limitations: It is important to note that Webflow may have certain limitations or requirements for domain setup. Ensure that your domain meets their guidelines, and if needed, reach out to Webflow support for further assistance.

In case you continue to experience issues with Webflow detecting the domain after following the steps above and ruling out any potential issues, it may be helpful to reach out to Webflow support for additional troubleshooting guidance.

Additional Questions:

1. How do I set up an A record in ClouDNS for my Webflow website?
2. Can I use a domain registered with ClouDNS for my Webflow website?
3. Why is my custom domain not working with Webflow even after DNS configuration?