DNS Made Easy

DNS Made Easy lets you point a custom domain to your Webflow site while keeping authoritative DNS with your existing provider.

Webflow handles hosting, CDN, and SSL, but not authoritative DNS for externally registered domains. Records that route traffic to Webflow must live in DNS Made Easy's control panel.

The integration adds Anycast routing for lower latency, failover monitoring, and a REST API for programmatic record management. You add three DNS records, verify the domain in Webflow, and SSL provisions automatically.

This fits agencies managing multiple client domains, DevOps teams treating DNS as infrastructure-as-code, and e-commerce operators who need health monitoring and failover during outages.

How to integrate DNS Made Easy with Webflow

What is DNS Made Easy? DNS Made Easy is a managed authoritative DNS hosting service operated under DigiCert, Inc. It provides DNS hosting, DNS failover with health monitoring, geographic traffic routing through its Global Traffic Director, and a REST API for programmatic DNS management.

Teams use DNS Made Easy with Webflow when they need DNS-layer reliability features beyond basic domain registration. Agencies onboarding multiple client domains can use DNS templates and the REST API. This standardizes Webflow DNS records across every domain they manage. Performance teams routing international traffic benefit from DNS Made Easy's Anycast network and geographic routing before Webflow's CDN layer handles content delivery.

The DNS Made Easy-Webflow integration supports 3 approaches:

• Manual DNS configuration handles the standard setup of A, CNAME, and TXT records through the DNS Made Easy control panel without writing code.
• ANAME records for apex domains let you point the root domain dynamically to Webflow's CDN hostname instead of a static IP address.
• The Webflow Data API and DNS Made Easy API give you control over domain provisioning, record management, and publish automation, but require server-side development.

Most implementations start with manual DNS configuration. Teams managing many domains or requiring infrastructure-as-code workflows add the API layer.

Configure DNS records in DNS Made Easy

This method covers the standard manual setup that connects a custom domain to a Webflow-hosted site. You create three DNS records in DNS Made Easy's control panel, verify the domain in Webflow, and SSL provisions automatically. Any DNS Made Easy plan tier supports this approach, and you need a paid Webflow site plan to connect a custom domain. Before starting, remove any existing A records on the root domain and CNAME records on www that point to a previous hosting provider.

To get your DNS values from Webflow:

1. Open your Webflow site dashboard and click Site Settings.
2. Go to the Publishing tab and find the Production section.
3. Click Add Custom Domain, then select Manually add domain.
4. Enter your domain name and click Add domain.
5. Copy the A record IP, CNAME target, and TXT verification string. Keep this tab open.

These values in Webflow are the ones you should use for your specific site.

To configure the records in DNS Made Easy:

1. Log into the DNS Made Easy control panel and select your domain under DNS > Managed DNS.
2. In the A Records section, click the + button. Set Name to @, IP Address to 198.202.211.1, and TTL to 3600. Click Submit.
3. In the CNAME Records section, click the + button. Set Name to www, Alias to cdn.webflow.com, and TTL to 3600. Click Submit.
4. In the TXT Records section, click the + button. Set Name to _webflow and paste the full one-time-verification=... string from your Webflow dashboard as the value. Set TTL to 3600. Click Submit.
5. Delete any other A records for @ or CNAME records for www that point to non-Webflow destinations. Do not delete MX, SPF, DKIM, or DMARC records.

Once these records are saved, DNS Made Easy is ready for Webflow verification.

To verify and publish in Webflow:

1. Return to Site Settings > Publishing > Production in Webflow.
2. Click Check status and wait for the domain to show as connected.
3. Set your root domain as the default domain.
4. Click Publish to push your site live on the custom domain.

After that publish step, your site can begin serving traffic on the connected domain.

SSL certificates provision automatically through Let's Encrypt and Google Trust Services after DNS propagation completes. Allow up to one hour after propagation for SSL to activate. No manual certificate setup is needed at any point.

DNS propagation typically finishes within a few hours, though it can take up to 48 hours globally. You can track propagation status across resolvers at whatsmydns.net. For faster propagation during setup, lower the TTL on your records to 30 seconds (DNS Made Easy's minimum) before making changes. Raise it to 3600 or higher after the domain is verified.

Use ANAME records for apex domain resolution

Standard DNS does not allow CNAME records at the zone apex (the root domain, like example.com). DNS Made Easy's proprietary ANAME record solves this by resolving the root domain dynamically to a hostname like cdn.webflow.com. This works similarly to how a CNAME functions for subdomains. Webflow maintains a dedicated integration page for this specific configuration. This approach avoids hardcoding Webflow's IP address, which could require a manual update if Webflow changes its infrastructure.

To configure an ANAME record:

1. In the DNS Made Easy control panel, navigate to your domain's DNS records.
2. Locate the ANAME Records section and click the + button.
3. Set Name to @ and Target to cdn.webflow.com.
4. Set TTL to 3600 and click Submit.
5. Remove any existing A records for the root domain that point to other destinations.

This setup keeps the apex pointed at Webflow through DNS Made Easy's ANAME mechanism.

ANAME resolution depends on DNS Made Easy's resolution of the target hostname. Webflow's official documentation recommends the standard A record (198.202.211.1) as the primary approach. Use ANAME only if dynamic resolution at the apex is a specific requirement for your architecture.

Build with the Webflow and DNS Made Easy APIs

For teams managing multiple Webflow domains or requiring infrastructure-as-code workflows, both platforms expose REST APIs that can be combined for programmatic DNS provisioning. This approach requires server-side development. It suits agencies onboarding client domains in bulk, DevOps engineers managing DNS alongside cloud infrastructure, or managed service providers building white-label deployment tools. DNS Made Easy API access requires a DNS-25 plan or higher, as the DNS-5 plan does not include API access.

The available APIs handle different parts of the workflow:

• The DNS Made Easy REST API manages DNS zones and records, authenticated with HMAC-SHA1 signed headers that combine an API key, secret key, and timestamp
• Webflow's Data API retrieves site and custom domain data and triggers site publishes
• Webflow webhooks fire events like site_publish that can trigger DNS operations on the DNS Made Easy side

Taken together, these APIs support end-to-end provisioning and validation workflows.

DNS Made Easy does not support outbound webhooks for DNS record changes. All event-driven automation uses Webflow's webhooks as the trigger source and DNS Made Easy's API as the action target.

Automate domain provisioning for new sites

Agencies onboarding new Webflow client sites can script the full DNS setup. A provisioning script creates the DNS zone, adds the required records, and confirms the domain is associated with the correct Webflow site.

To implement automated provisioning:

1. Call POST https://api.dnsmadeeasy.com/V2.0/dns/managed/ with the body {"name":"clientdomain.com"} to create the DNS zone. Store the returned domainId.
2. Call POST https://api.dnsmadeeasy.com/V2.0/dns/managed/{domainId}/records/ three times to create the A record ({"name":"@","type":"A","value":"198.202.211.1","ttl":3600}), CNAME record ({"name":"www","type":"CNAME","value":"cdn.webflow.com","ttl":3600}), and TXT verification record ({"name":"_webflow","type":"TXT","value":"one-time-verification=xxxxx","ttl":300}).
3. Call GET https://api.webflow.com/v2/sites to retrieve all site IDs, then GET https://api.webflow.com/v2/sites/{site_id}/custom_domains to confirm domain association before triggering a publish.

This gives agencies a repeatable provisioning flow for new client domains.

Implement exponential backoff for larger batches and test automation scripts in DNS Made Easy's sandbox environment at https://api.sandbox.dnsmadeeasy.com/V2.0/ before running against production zones.

Trigger DNS updates on Webflow publish events

You can register a Webflow webhook that fires on every site publish. The event then triggers DNS record updates or validation checks through DNS Made Easy's API.

To set up publish-triggered DNS automation:

1. Call POST https://api.webflow.com/v2/sites/{site_id}/webhooks with the body {"triggerType": "site_publish", "url": "https://your-handler-endpoint.com/webhook"} to register the webhook.
2. In your webhook handler, parse the incoming site_publish payload for the site ID and publish event details.
3. Call DNS Made Easy's GET https://api.dnsmadeeasy.com/V2.0/dns/managed/{domainId}/records?type=A to verify current records match expected Webflow values. Use PUT to update any records that have drifted.

This pattern works for blue-green deployments where DNS records switch between two Webflow sites. It also supports compliance workflows that audit DNS state after every publish event. In both cases, Webflow provides the event trigger and DNS Made Easy provides the DNS action layer.

What can you build with the DNS Made Easy Webflow integration?

Integrating DNS Made Easy with Webflow lets you manage production DNS for Webflow-hosted sites without giving up enterprise DNS features or automation capabilities.

• Multi-client agency provisioning: Agencies managing dozens of Webflow client sites can use DNS Made Easy's REST API and DNS templates to create standardized record sets for every new domain. A provisioning script replaces manual control panel work and reduces configuration errors across the client portfolio.
• DNS failover for e-commerce storefronts: An online store running on Webflow can configure DNS Made Easy's failover monitoring to check site health every two to four minutes. Traffic redirects to a backup IP if the primary becomes unreachable. This adds a DNS-layer recovery mechanism independent of Webflow's hosting.
• Geographic traffic routing for international sites: A company with visitors across multiple continents can use DNS Made Easy's Global Traffic Director. DNS queries route based on the requesting resolver's location, reducing DNS latency before Webflow's CDN serves content.
• Infrastructure-as-code DNS management: DevOps teams managing a Webflow marketing site alongside cloud application infrastructure can define DNS records in Terraform or octoDNS. DNS configuration enters the standard code review and deployment pipeline, version-controlled and auditable alongside application infrastructure.

If you need more control over bulk domain migrations or automated publish-triggered DNS validation, the API integration path covers those cases with full flexibility.