| Objective | Connect your domain to a Webflow site using manual DNS records. |
| Why customers use this | Lets you use Webflow design tools with your own domain; Keeps AEserver as the registrar of record |
| Records to expect | Webflow provides the exact A records for the root domain and a CNAME for www in the project settings. |
Before you start
Have access to both your AEserver Client Area and your account at Webflow.
Know whether you are connecting the root domain (example.com), a subdomain (such as www.example.com or shop.example.com), or both.
Take a quick screenshot or copy of any current DNS records before editing them, especially if the domain already has a live website or email service.
Step 1 – Get the DNS records from Webflow
1. Log in to Webflow and open the project.
2. Go to Site settings > Publishing > Production.
3. Click Add a custom domain or Manually add domain.
4. Enter your domain and copy the DNS records Webflow displays.
Step 2 – Add the records in the AEserver Client Area
1. Sign in to your AEserver Client Area and open your domain.
2. Go to DNS Management.
3. Add the A records for the root domain exactly as provided by Webflow.
4. Add the www CNAME record using the value shown in Webflow.
5. Save all changes.
Step 3 – Verify and finish
1. Go back to Webflow, publish the site to the custom domain, and set the default domain if prompted.
2. Allow time for DNS propagation. Many changes appear within a few minutes or hours, but full propagation can take up to 24-48 hours.
3. Once the service shows as connected, test the live result. Open the website, send a test email, or visit the exact subdomain you connected.
Benefits to highlight in the KB article
Lets you use Webflow design tools with your own domain
Keeps AEserver as the registrar of record
Supports a clean launch workflow for landing pages and company sites
Quick tips
Webflow usually needs both the root domain and www configured
Publish the site after DNS is in place or visitors may still see a placeholder
If your old website was on the same domain, expect temporary cache differences
Common issues and solutions
| Common problems | What it usually means / what to do |
| Root domain works but www does not | The www CNAME is missing or points to the wrong target |
| Webflow says the domain is not verified | Wait longer, then review spelling and duplicates |
| Old traffic lands on another site | Check for legacy A records or proxy/CDN settings still active |
If you are not sure which record to edit, or if the domain already has a working website or email service, contact AEserver Support before making changes so we can help you avoid downtime.
