Summarize this blog post with: ChatGPT | Perplexity | Claude | Grok

You already know that connecting a domain is one of the final steps before launching a Cloudways website. What is less obvious is that Cloudways Flexible, Cloudways Autonomous, DNS Made Easy, and personal Cloudflare accounts do not use the same DNS workflow. In this guide, you will learn which setup applies to you, which records to add, and how to fix propagation, SSL, email, and domain-verification problems.

Last verified: August 2, 2026.

For broader platform configuration, use this complete Cloudways tutorial alongside the DNS instructions below.

Key Takeaways

• Cloudways DNS refers to the DNS configuration connecting a custom domain to a Cloudways application, not a universal nameserver service included with every Cloudways product.
• Cloudways Flexible domains normally use A records at the registrar, Cloudflare, DNS Made Easy, or another authoritative DNS provider.
• Cloudways Autonomous domains connect through integrated Cloudflare Enterprise using account-specific CNAME records or alternative A records.
• DNS Made Easy is an optional paid add-on that moves authoritative DNS management into the Cloudways Platform.
• Email records such as MX, SPF, DKIM, DMARC, Autodiscover, and verification records must be preserved during a nameserver change.
• DNS propagation should be checked through authoritative nameservers and multiple recursive resolvers, not by repeatedly refreshing one browser.
• SSL installation and HTTPS redirection should be completed only after the required domain records resolve to the correct destination.

What Is Cloudways DNS and How Does It Work?

Cloudways DNS is the configuration that connects a custom domain to a Cloudways-hosted application. The term covers the A, CNAME, MX, TXT, and other records needed to route website, email, verification, and subdomain traffic correctly.

Cloudways DNS does not mean that every Cloudways customer receives a fixed pair of Cloudways nameservers. Cloudways Flexible users normally manage authoritative DNS through their registrar, Cloudflare, DNS Made Easy, or another DNS provider. Cloudways Autonomous uses an integrated Cloudflare Enterprise workflow for custom domains.

A domain can therefore involve three separate services:

• Domain registrar: The company where the domain is registered.
• Authoritative DNS provider: The service whose nameservers publish the active DNS zone.
• Web host: The platform serving the website files and application.

For example, a domain may be registered with Namecheap, use Cloudflare nameservers, and host WordPress on Cloudways. Changing records inside Namecheap would have no effect in that configuration because Cloudflare is authoritative.

Cloudways also distinguishes between mapping a domain inside the platform and publishing DNS records publicly. Adding example.com under Domain Management tells Cloudways which hostname belongs to the application, while the public A or CNAME record tells internet resolvers where that hostname should go.

A detailed Cloudways hosting review can help prospective users evaluate the hosting platform separately from its DNS workflow.

Does Cloudways Provide DNS Hosting or Nameservers?

Cloudways does not provide universal built-in nameservers for standard DNS resolution. Its official documentation directs users to manage DNS through their registrar or another provider, while offering DNS Made Easy as an optional authoritative DNS integration.

This distinction prevents a common mistake: searching the Cloudways dashboard for nameservers that do not exist for a normal Flexible setup. In most cases, you only need to update records at the provider already listed in your domain’s NS lookup.

How Do You Identify the Authoritative DNS Provider?

The authoritative DNS provider is the service named in the domain’s active NS records. The registrar and DNS provider may be the same company, but they do not have to be.

Run one of these commands:

dig NS example.com +short

nslookup -type=NS example.com

You can also use Google Admin Toolbox Dig, DNSChecker, or another NS lookup tool. If the result contains Cloudflare nameservers, manage records in Cloudflare. If it contains Namecheap BasicDNS nameservers, manage records in Namecheap.

[Insert image: Display an NS lookup showing the active authoritative nameservers | Alt text: “Identify Cloudways DNS provider with an NS lookup”]

Why Does Correct Cloudways DNS Configuration Matter?

Correct Cloudways DNS configuration matters because DNS controls whether visitors, certificate authorities, mail servers, crawlers, and third-party services can reach the intended destination. An incorrect record can leave the temporary Cloudways URL working while the public domain shows an old website, fails SSL validation, or stops receiving email.

“DNS records contain information about your domain and are used to make your website or application available to visitors and other web services.”

— Cloudflare Documentation Team, Cloudflare DNS Docs, 2026

The quote matters because website traffic is only one part of a DNS zone. A successful migration must preserve every service that depends on the domain, including email, analytics verification, payment services, support portals, and transactional mail.

Correct configuration affects the following areas:

• Website availability: The apex and www hostnames must resolve correctly.
• SSL issuance: Let’s Encrypt must be able to validate the requested domain.
• Cloudflare activation: Verification records must match the values supplied by Cloudways.
• Email delivery: MX and authentication records must remain intact.
• Subdomain routing: Each application or service needs the correct destination.
• Migration continuity: Low TTLs and rollback data reduce cutover risk.
• SEO consistency: The preferred hostname, redirects, canonical tags, and sitemap URLs should agree.
• Conversion protection: DNS failures can interrupt checkouts, lead forms, logins, and customer support.

A website can function through its Cloudways application URL while remaining inaccessible through its custom domain. The application URL verifies that the server works; it does not prove that public DNS is correct.

→ Explore Cloudways DNS Options

Which Cloudways DNS Setup Should You Choose?

The correct Cloudways DNS setup depends on the Cloudways product, the active authoritative DNS provider, and whether you are changing individual records or replacing nameservers. Identify those three factors before editing the zone.

The Cloudways Flexible vs Autonomous comparison provides additional context about how the products differ beyond DNS.

Cloudways DNS Decision Tree

Use this sequence:

1. Are you using Flexible or Autonomous?
   • Flexible usually points directly to the Cloudways server IP.
   • Autonomous connects through Cloudflare Enterprise.
2. Who is authoritative for the domain?
   • Check the NS records.
   • Make changes only at that provider.
3. Are you changing records or changing nameservers?
   • A record change updates one destination.
   • Nameserver replacement moves the entire authoritative zone.
4. Are you using personal Cloudflare, Cloudways Cloudflare Enterprise, or DNS Made Easy?
   • These are different workflows and should not be combined blindly.
5. Does the domain use email or third-party verification records?
   • Inventory and recreate those records before any nameserver cutover.

[Insert image: Show a Cloudways DNS decision tree for Flexible, Autonomous, Cloudflare, and DNS Made Easy | Alt text: “Choose the correct Cloudways DNS setup workflow”]

For readers still selecting a hosting configuration, compare Cloudways hosting plans before committing to a product-specific DNS workflow.

How Should You Prepare a Domain Before Changing Cloudways DNS?

Preparing a domain for Cloudways DNS requires a complete zone inventory, a tested application, a known rollback path, and confirmation of the active nameservers. DNS changes should begin only after the destination application works independently of the public domain.

Use the following zero-downtime framework:

Inventory → Prepare → Prevalidate → Lower TTL → Cut over → Verify → Monitor → Roll back if necessary

Pre-change Checklist

• Confirm whether the application uses Cloudways Flexible or Autonomous.
• Test the application through its temporary Cloudways URL.
• Add the custom domain under Cloudways Domain Management.
• Select the preferred primary domain.
• Copy the Flexible server IP or Autonomous target records.
• Query and record the current authoritative nameservers.
• Export, copy, or screenshot the current DNS zone.
• Record all A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, and verification records.
• Identify which service owns each record.
• Check whether DNSSEC is enabled.
• Note the previous web-server IP.
• Test the migrated site before public cutover.
• Prepare a rollback instruction for the previous destination.
• Lower the relevant TTL at least one existing TTL cycle before a planned cutover.

For a WordPress move, complete the application work using a WordPress-to-Cloudways migration guide before changing public DNS.

Cloudways DNS Inventory Template

Why DNSSEC Must Be Checked Before Changing Nameservers

DNSSEC must be coordinated with a nameserver change because an old DS record can cause validating resolvers to return SERVFAIL. Cloudflare documents that changing authoritative nameservers without updating or allowing the old DS data to expire can create a mismatch between the parent zone and the new provider’s signing keys.

A DNSSEC failure differs from ordinary propagation. Correct A and CNAME records may exist at the new provider while users still receive SERVFAIL because the delegation chain cannot be validated.

How Do You Point a Domain to Cloudways Flexible?

Pointing a domain to Cloudways Flexible involves adding the domain in Cloudways Domain Management and creating A records that resolve to the server’s public IPv4 address. The records must be added at the active authoritative DNS provider, not necessarily the registrar.

“An A Record maps your domain name to the public IP address of your server.”

— Syed Abuzar Mehdi, Cloudways Help Center, 2025

The A record provides the direct mapping used by Cloudways Flexible. The server IP is account-specific, so you must copy it from your own Cloudways application or server information rather than using an IP from a tutorial.

Step 1: Add the Domain in Cloudways

1. Log in to the Cloudways Platform.
2. Open Flexible.
3. Select My Servers.
4. Open the server hosting the application.
5. Select the target application.
6. Open Domain Management.
7. Click Add Domain.
8. Enter the root domain.
9. Save the change.
10. Open the domain options and select Make Primary for the preferred hostname.

Cloudways currently adds the www version when a root domain is added in Domain Management, but public DNS still needs to resolve the required hostnames.

[Insert image: Show the Flexible application Domain Management screen with Add Domain and Make Primary controls | Alt text: “Add a custom domain in Cloudways Flexible”]

Step 2: Copy the Cloudways Server IP

Open the server or application information area and copy the public IPv4 address. Do not copy the private IP, database IP, temporary URL, or an IP shown in another person’s tutorial.

Step 3: Add the Required DNS Records

Cloudways documents A-record examples for the root domain, www, named subdomains, and wildcard subdomains.

An alternative www setup is:

Both approaches can work. An A record sends www directly to the server IP, while a CNAME makes www follow the root hostname. The CNAME approach reduces duplicated IP updates, but the root domain must resolve correctly.

Step 4: Remove Conflicting Records

Check for:

• An old A record for @
• An old A or CNAME record for www
• An obsolete AAAA record
• A URL-forwarding record
• A parking record
• Duplicate records pointing to different servers

An obsolete AAAA record is particularly easy to overlook. Some visitors may use IPv6 and reach the old destination even though the A record correctly points IPv4 traffic to Cloudways.

Step 5: Verify, Install SSL, and Enable Redirects

Verify the new A record through authoritative and public resolver queries. After the domain resolves correctly, install or renew SSL and then enable one HTTPS-redirection layer.

The standalone connect a domain to Cloudways tutorial can be used for registrar-specific screenshots.

Watch: Point a Domain to Cloudways and Install SSL

This official Cloudways walkthrough demonstrates how to configure a domain through a registrar, point it to a Cloudways application, and install and manage the SSL certificate.

Video: “How to Point Domains and Install SSL Certificates on Cloudways | Cloudways 101” by Cloudways.

Which A Records Should You Add for a Cloudways Domain?

A standard Cloudways Flexible domain normally needs an apex A record and a record for the www hostname. Add subdomain or wildcard records only when the application is configured to serve those hostnames.

Avoid adding a wildcard record merely as a precaution. A wildcard can route mistyped or unintended subdomains to the application and may complicate SSL, multisite, or SaaS verification.

Should the www Record Use an A Record or CNAME?

The www hostname can normally use either an A record pointing to the Cloudways IP or a CNAME pointing to the root domain. A CNAME is often easier to maintain because a future root-IP change does not require a separate www update.

Do not place another record type at the same hostname as a conventional CNAME when the DNS provider prohibits that combination.

How Do You Add a Subdomain or Wildcard Domain?

A Cloudways Flexible subdomain uses an A record for the subdomain label, while a wildcard uses * as the hostname. The hostname must also be mapped to the intended Cloudways application.

Examples:

A    blog    203.0.113.10
A    shop    203.0.113.10
A    *       203.0.113.10

A specific record normally takes precedence over a wildcard. For example, a dedicated shop record can direct shop.example.com elsewhere while the wildcard handles other undefined subdomains.

How Do You Connect a Domain to Cloudways Autonomous?

Connecting a domain to Cloudways Autonomous requires adding the custom domain in the Autonomous application and publishing the CNAME or fallback A records supplied by Cloudways. Autonomous uses integrated Cloudflare Enterprise, so Flexible server-IP instructions should not be substituted.

Cloudways states that Autonomous applications use built-in Cloudflare Enterprise for domain verification, CDN delivery, edge caching, security, and DDoS protection.

Cloudways Autonomous Setup Steps

1. Log in to Cloudways.
2. Select Autonomous from the side menu.
3. Open My Applications.
4. Select the target application.
5. Choose Add Custom Domain or Manage Access.
6. Open Domain Management.
7. Add the root domain or subdomain.
8. Allow Cloudways to begin ownership verification.
9. Click View CNAME Records.
10. Copy the displayed hostnames and targets exactly.
11. Add those records at the authoritative DNS provider.
12. Use fallback A records only when the provider cannot support an apex CNAME.
13. Set external Cloudflare records to DNS only during the required verification process.
14. Return to Cloudways and monitor the domain status.
15. Confirm that the status changes to Domain is Live.

Cloudways’ current public instructions show secure.cloudwayssites.com as an Autonomous CNAME target in its take-site-live guide. However, the values displayed inside the application dashboard should remain the source of truth for an individual account.

[Insert image: Show the Cloudways Autonomous View CNAME Records panel | Alt text: “Copy Cloudways Autonomous DNS records for a custom domain”]

What Happens When an Apex CNAME Is Unsupported?

An apex CNAME limitation occurs when a DNS provider does not allow a conventional CNAME at @. Cloudways provides alternative A records for this situation and recommends adding both displayed A records when possible for reliability.

Cloudflare DNS supports apex CNAME behavior through CNAME flattening, which returns resolved IP addresses to DNS clients. Other providers may offer ALIAS or ANAME records instead.

Never invent an Autonomous fallback IP. Copy the values currently displayed in your Cloudways application.

Why Does Autonomous Show “Domain Is Not Live”?

“Domain is not live” means Cloudways has not yet verified that the published records resolve to the expected Cloudflare Enterprise destination. The likely causes are incomplete propagation, incorrect hostnames, wrong targets, conflicting records, or proxied verification records.

Cloudways states that Autonomous verification may take up to 24 hours depending on the DNS provider and cached responses. The status changes automatically after the required records propagate.

What Is the Cloudways DNS Made Easy Add-on?

DNS Made Easy is an optional Cloudways add-on that lets users manage authoritative DNS records through the Cloudways Platform. Activating it changes where the DNS zone is hosted and requires replacing the domain’s current nameservers with the nameservers supplied by the add-on.

Cloudways Flexible does not require DNS Made Easy. Registrar DNS or Cloudflare is sufficient for many websites. DNS Made Easy becomes more attractive when an agency wants centralized record administration, query monitoring, failover options, and consistent team access.

Current DNS Made Easy Pricing

As of August 2, 2026, Cloudways lists:

• $0.50 per domain per month
• 500,000 included DNS queries per domain each month
• $0.10 per additional 100,000 queries
• Account-level pooling of the included query allowance

— Source: Cloudways Help Center, 2026. Pricing and billing rules should be rechecked before publication or purchase because commercial terms can change.

See the related Cloudways pricing and add-on costs guide for broader cost analysis.

→ Compare Cloudways Plans

How to Activate DNS Made Easy

1. Log in to Cloudways.
2. Open Integrations.
3. Select DNS Made Easy.
4. Click Get Started.
5. Add the domain.
6. Recreate every required DNS record.
7. Click Configure Nameservers.
8. Copy the supplied nameservers.
9. Replace the old nameservers at the registrar.
10. Monitor the domain until its status becomes active.

Cloudways currently requires the nameserver update within 48 hours after adding a domain. A domain whose nameservers remain unchanged may be removed from the platform after that window.

[Insert image: Show the DNS Made Easy integration page with Add Domain and Configure Nameservers | Alt text: “Activate Cloudways DNS Made Easy and configure nameservers”]

Why the Full Zone Must Be Recreated First

A nameserver change does not automatically copy records from the old DNS provider. Website, email, verification, and SaaS records must exist in the new zone before or during delegation.

Cloudways and Namecheap both warn that records are not automatically transferred when nameservers change.

A safe sequence is:

1. Export the old zone.
2. Build the new DNS Made Easy zone.
3. Compare every hostname and value.
4. Confirm MX and authentication records.
5. Lower old NS or relevant record TTLs where possible.
6. Change nameservers.
7. Query the new authoritative servers directly.
8. Monitor the website and email.

Is DNS Made Easy Necessary for Cloudways?

DNS Made Easy is not necessary for a standard Cloudways website. Use it when centralized control, multi-domain administration, failover features, or Cloudways-based team access justify the additional cost and migration complexity.

→ Evaluate Cloudways Hosting

How Do You Configure Cloudways DNS Through a Personal Cloudflare Account?

A personal Cloudflare setup requires moving authoritative DNS to Cloudflare, reviewing imported records, and pointing the required hostnames to Cloudways. This workflow applies when you are not already using the Cloudways Cloudflare Enterprise integration for the same application.

Cloudways states that customers with its Cloudflare Enterprise integration do not need to activate a separate personal Cloudflare CDN configuration for the application.

Watch: How Cloudways Cloudflare Enterprise Integration Works

Before configuring a personal Cloudflare account, watch this official walkthrough of the Cloudways-managed Cloudflare Enterprise workflow. It will help you understand why the Enterprise integration and a separate personal Cloudflare setup should not be treated as the same configuration.

Video: “How to Integrate Cloudflare CDN With Your Website | Cloudways 101” by Cloudways.

Personal Cloudflare Setup Steps

1. Create or open a Cloudflare account.
2. Add the domain.
3. Review every automatically imported DNS record.
4. Add any missing MX, TXT, CNAME, SRV, and verification records.
5. Copy the two Cloudflare nameservers.
6. Replace the current nameservers at the registrar.
7. Wait for Cloudflare to confirm activation.
8. Add or update the root and www records for Cloudways.
9. Keep records DNS-only during origin testing or provider verification where required.
10. Install a valid certificate at the Cloudways origin.
11. Select an appropriate Cloudflare SSL/TLS mode.
12. Enable proxying only after the origin works correctly.
13. Purge Cloudflare, Cloudways, Breeze, Varnish, and browser caches as applicable.

Cloudways documents the process of adding a personal Cloudflare account, reviewing the zone, and replacing registrar nameservers with Cloudflare’s assigned nameservers.

[Insert image: Show Cloudflare DNS records with orange-cloud and DNS-only status controls | Alt text: “Configure Cloudflare DNS records for Cloudways hosting”]

A dedicated Cloudways Cloudflare setup guide can provide additional caching and security configuration.

What Is the Difference Between Proxied and DNS-Only Records?

A proxied Cloudflare record routes supported web traffic through Cloudflare, while a DNS-only record returns the configured origin destination directly. Proxying can provide CDN and security benefits, but it can also hide the origin during troubleshooting or interfere with certain validation records.

Use DNS only when:

• Cloudways specifically requires DNS-only verification.
• You are diagnosing the origin.
• A third-party CNAME validation must return its exact target.
• A service is not compatible with Cloudflare proxying.
• Mail or non-web records are involved.

Use Proxied when:

• The website is already verified.
• The origin certificate works.
• Cloudflare is intended to protect and accelerate HTTP traffic.
• The record type and service support proxying.

Cloudflare documents that domain-verification CNAME records can fail when proxied or flattened unexpectedly.

Which Cloudflare SSL Mode Should You Use?

Cloudflare Full (strict) is the preferred SSL mode when the Cloudways origin presents a valid, unexpired certificate matching the requested hostname. Flexible mode encrypts only the visitor-to-Cloudflare connection and can contribute to redirect loops when the origin forces HTTPS.

“For the best security, choose Full (strict) mode whenever possible.”

— Cloudflare Documentation Team, Cloudflare SSL/TLS Docs, 2026

Full (strict) validates the origin certificate, hostname, and expiry. Cloudflare recommends Full or Full (strict) rather than an unencrypted origin connection.

A common redirect loop occurs when Cloudflare uses Flexible mode while WordPress or Cloudways redirects all origin requests to HTTPS. The browser requests HTTPS, Cloudflare contacts the origin over HTTP, and the origin redirects back to HTTPS repeatedly.

Which DNS Records Are Used with Cloudways?

Cloudways configurations primarily depend on A, CNAME, MX, TXT, and NS records, while AAAA, CAA, SRV, PTR, and SOA records support specific network, security, and service requirements. Each record should have a documented owner and purpose before a migration.

Cloudflare defines TTL as the period for which resolvers cache a response before revalidation. Proxied records use an automatic TTL, while DNS-only records generally allow configurable values.

Why Obsolete AAAA Records Cause Intermittent Failures

An obsolete AAAA record can send IPv6-capable visitors to a different server than the A record. The result may appear random because some networks prefer IPv6 while others use IPv4.

Check both records:

dig A example.com
dig AAAA example.com

Remove an AAAA record only after confirming that the hostname should not resolve through that IPv6 address.

How Apex Domains Differ from Subdomains

An apex domain is the bare hostname such as example.com, while a subdomain adds a label such as www.example.com or blog.example.com. Conventional DNS standards make apex CNAME handling more complicated because the apex must also contain records such as SOA and NS.

Cloudflare handles apex hostnames using CNAME flattening. Other providers may require A records, ALIAS records, or ANAME records.

How Do You Change Cloudways DNS Without Breaking Email?

Changing Cloudways DNS without breaking email requires preserving every mail-routing, authentication, discovery, and verification record in the authoritative zone. Changing only a website A record normally leaves email untouched, but replacing nameservers can remove the entire mail configuration.

Changing nameservers without recreating MX, SPF, DKIM, and DMARC records can interrupt email even when the website’s A record is correct.

Email DNS Preservation Checklist

Record and verify:

• MX records and priorities
• SPF TXT record
• DKIM selectors
• DMARC policy
• Provider-verification TXT records
• Autodiscover CNAME or SRV records
• Mail-related CNAME records
• Transactional-email SPF and DKIM records
• Help desk or CRM verification records
• Custom tracking domains
• Return-path or bounce-processing records

Web hosting and email hosting can use different providers. For example, WordPress can run on Cloudways while inbound mail remains with Google Workspace.

Provider-Specific Record Families

Google currently documents smtp.google.com for new Google Workspace MX setups while noting that functioning legacy aspmx configurations do not require replacement. Microsoft advises copying account-specific DNS values from the Microsoft 365 Admin Center.

Rackspace warns that competing MX records can cause mail complications, while Elastic Email instructs users to combine authorized senders into one SPF policy rather than publishing multiple SPF records.

Do not copy generic email values from a third-party tutorial. Use the exact tenant, selector, token, priority, and target displayed by the provider.

[Insert image: Show Google Workspace MX records in the Admin setup tool | Alt text: “Preserve Google Workspace DNS records during Cloudways migration”]

[Insert image: Show Microsoft 365 domain DNS requirements in the Admin Center | Alt text: “Copy Microsoft 365 DNS records before changing nameservers”]

[Insert image: Show Rackspace Cloud Office DNS record requirements | Alt text: “Review Rackspace Email DNS records before Cloudways cutover”]

[Insert image: Show Elastic Email domain verification with SPF and DKIM status | Alt text: “Verify Elastic Email DNS records with Cloudways hosting”]

For hosting-and-mail architecture options, see Cloudways email hosting options.

How to Test Email After the DNS Change

Complete these checks:

1. Query the public MX records.
2. Confirm that SPF returns one valid policy.
3. Query each DKIM selector.
4. Query _dmarc.example.com.
5. Send an inbound test from an external provider.
6. Send an outbound message.
7. Inspect authentication results in the message headers.
8. Test Autodiscover or mail-client setup.
9. Test transactional messages from WordPress or WooCommerce.
10. Monitor bounce and rejection logs.

Example commands:

dig MX example.com +short
dig TXT example.com +short
dig TXT selector1._domainkey.example.com +short
dig TXT _dmarc.example.com +short

How Do You Install SSL After Cloudways DNS Is Correct?

Cloudways SSL installation should begin only after every requested hostname resolves to the expected Cloudways destination. The root and www versions must both be mapped when both are included on the certificate.

Cloudways lists correct domain mapping and DNS resolution as SSL prerequisites. Its documentation also states that www must point through an A record or CNAME before that hostname can be added to a Let’s Encrypt certificate.

Cloudways Flexible SSL Steps

1. Confirm root and www DNS resolution.
2. Open the Cloudways application.
3. Select SSL Certificate.
4. Choose Let’s Encrypt.
5. Enter a valid email address.
6. Add the root domain.
7. Add additional hostnames where required.
8. Install the certificate.
9. Verify the certificate externally.
10. Enable HTTPS redirection in only one layer.

The Cloudways SSL certificate setup guide can cover application-specific screenshots and renewal checks.

[Insert image: Show the Cloudways Let’s Encrypt SSL installation form | Alt text: “Install a Cloudways SSL certificate after DNS propagation”]

How Wildcard SSL DNS Validation Works

A Cloudways Let’s Encrypt wildcard certificate requires DNS authentication through an _acme-challenge CNAME record. The record points to the account-specific Cloudways application FQDN shown during installation.

Cloudways advises keeping the validation CNAME because deleting it can prevent automatic wildcard-certificate renewal.

Example structure:

Type: CNAME
Host: _acme-challenge
Target: account-specific Cloudways application FQDN

Why SSL Installation Fails After a DNS Change

Common causes include:

• Root or www resolves to the old server.
• One requested hostname has no DNS record.
• A conflicting AAAA record points elsewhere.
• The _acme-challenge CNAME is missing.
• Cloudflare proxying obscures a required validation response.
• CAA records prevent Let’s Encrypt issuance.
• The domain is mapped to the wrong Cloudways application.
• Cached DNS answers have not expired.

Do not enable multiple redirect systems simultaneously. Cloudways notes that HTTPS redirection can be handled at the platform, firewall, or application layer, but competing mechanisms should be disabled to prevent conflicts.

How Can You Check Whether Cloudways DNS Has Propagated?

Cloudways DNS propagation is the period during which authoritative changes become visible as recursive resolvers replace cached answers. Different users can receive different results temporarily because their resolvers may hold responses cached under different TTLs.

DNS propagation is not the same as browser caching. Clearing a browser cache does not force an ISP, office network, public resolver, or authoritative nameserver to change its DNS answer.

The Three-Layer DNS Verification Method

Check three layers:

1. Authoritative nameserver: Confirms what the DNS provider currently publishes.
2. Public recursive resolver: Confirms what a major resolver currently returns.
3. Local resolver: Confirms what your device or network sees.

Example:

dig NS example.com +short
dig A example.com @authoritative-nameserver.example
dig A example.com @1.1.1.1
dig A example.com @8.8.8.8
dig A example.com

Interpretation:

• If the authoritative answer is wrong, fix the zone.
• If the authoritative answer is correct but public resolvers differ, cached responses are still expiring.
• If public resolvers are correct but your local answer is old, flush the local or network cache.

Useful Cloudways DNS Propagation Tools

• Cloudways domain status
• WhatsMyDNS
• DNSChecker
• Google Admin Toolbox Dig
• Cloudflare DNS dashboard
• dig
• nslookup
• whois or registrar NS tools

Cloudways recommends third-party propagation checkers such as WhatsMyDNS for reviewing A and CNAME resolution across locations.

[Insert image: Show global A-record results in WhatsMyDNS | Alt text: “Check Cloudways DNS propagation across global resolvers”]

[Insert image: Show an A and MX lookup in Google Admin Toolbox Dig | Alt text: “Verify Cloudways DNS records with Google Admin Toolbox”]

[Insert image: Show DNSChecker results for root and www records | Alt text: “Compare Cloudways DNS propagation with DNSChecker”]

[Insert image: Show dig commands comparing authoritative and recursive answers | Alt text: “Troubleshoot Cloudways DNS with dig commands”]

How Long Does Cloudways DNS Propagation Take?

Cloudways DNS propagation can take minutes, hours, or longer depending on TTL, resolver caching, record type, and whether nameservers were changed. No single duration should be presented as a guarantee.

Cloudways’ documentation references windows ranging from several minutes for some validation records to 24 hours for Autonomous verification and 24–48 hours for nameserver changes.

The useful question is not “Has enough time passed?” but “What does the authoritative nameserver publish right now?”

How to Clear Local DNS Caches

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux with systemd-resolved:

sudo resolvectl flush-caches

Also restart the browser, test in a private window, change networks, or query a public resolver directly. These steps affect local testing but do not accelerate global resolver expiration.

Why Is Cloudways DNS Not Working?

Cloudways DNS usually fails because the wrong provider was edited, a required hostname is missing, a conflicting record remains, verification is proxied, or cached answers still point to the previous destination. Troubleshooting should begin with authoritative DNS rather than application settings.

Why Does the Root Domain Work but www Does Not?

The root domain works while www fails when www.example.com has no valid A or CNAME record. Adding the root domain inside Cloudways does not guarantee that every public DNS provider automatically creates a www record.

Query it directly:

dig A www.example.com
dig CNAME www.example.com

Why Does Cloudways Say “Domain Is Not Live”?

Cloudways displays “Domain is not live” when its verification system cannot see the expected DNS target. Check the exact hostname, target, proxy status, duplicate records, and authoritative nameservers.

For Autonomous, use the CNAME or fallback A values displayed in the application. For Flexible, confirm that the A record matches the application server’s public IP.

Why Does Cloudways SSL Installation Fail?

Cloudways SSL installation fails when one or more certificate hostnames do not resolve correctly or a validation record cannot be reached. Verify root, www, additional domains, and _acme-challenge records before reinstalling.

How Do You Roll Back a Failed DNS Migration?

A Cloudways DNS rollback restores the previous working record or nameserver delegation while preserving evidence of the failed configuration. The correct rollback method depends on whether you changed individual records or authoritative nameservers.

For a record-only change:

1. Restore the previous A, AAAA, or CNAME value.
2. Leave unrelated email records untouched.
3. Query the authoritative server.
4. Monitor public resolvers.

For a nameserver migration:

1. Restore the previous nameservers at the registrar.
2. Confirm that the previous DNS zone still exists.
3. Coordinate DNSSEC and DS records.
4. Query the restored authoritative servers directly.
5. Continue monitoring website and email traffic.

Do not delete the failed new zone immediately. Keep it available for comparison and correction.

How Do You Configure Common Cloudways DNS Scenarios?

Common Cloudways DNS scenarios can be handled safely by separating website routing, mail routing, subdomain ownership, proxying, and indexing controls. Each hostname should have one documented purpose and one expected destination.

Root and www on Cloudways Flexible

A       @       CLOUDWAYS_SERVER_IP
CNAME   www     example.com

Use an A record for www instead when your provider or operational standard prefers direct mappings.

Root and www on Cloudways Autonomous

CNAME   @       CLOUDWAYS_SUPPLIED_TARGET
CNAME   www     CLOUDWAYS_SUPPLIED_TARGET

Use the A-record alternatives displayed by Cloudways when the provider rejects an apex CNAME. Do not substitute generic addresses.

Blog Subdomain on the Same Flexible Server

A       blog    CLOUDWAYS_SERVER_IP

Add blog.example.com to the intended application’s Domain Management area and include it in SSL.

Subdomain Hosted on a Separate Server

A       @       CLOUDWAYS_SERVER_IP
A       app     SEPARATE_SERVER_IP

A wildcard pointing to Cloudways should not override the documented app record because a specific hostname normally takes precedence.

Personal Cloudflare with Cloudways

A       @       CLOUDWAYS_SERVER_IP        Proxied after testing
CNAME   www     example.com                Proxied after testing
MX      @       MAIL_PROVIDER_TARGET       DNS only

Keep verification and mail records DNS-only.

DNS Made Easy with Cloudways

Recreate the entire zone before changing nameservers:

A       @       CLOUDWAYS_SERVER_IP
CNAME   www     example.com
MX      @       MAIL_PROVIDER_TARGET
TXT     @       SPF_POLICY
TXT     _dmarc  DMARC_POLICY

Google Workspace Email with Cloudways Hosting

A       @       CLOUDWAYS_SERVER_IP
CNAME   www     example.com
MX      @       GOOGLE_WORKSPACE_VALUE
TXT     @       SPF_POLICY
TXT     selector._domainkey   GOOGLE_DKIM_VALUE
TXT     _dmarc  DMARC_POLICY

Copy the current Google values from the Admin console because legacy and new configurations may differ.

WooCommerce Migration with Minimized Downtime

A safe ecommerce cutover includes:

1. Lowering the current A-record TTL in advance.
2. Migrating and testing the store.
3. Scheduling a brief order freeze or final database synchronization.
4. Updating the A record.
5. Testing checkout, payment callbacks, webhooks, and transactional email.
6. Monitoring both old and new servers during cache expiry.
7. Keeping the previous IP available for rollback.

The Cloudways WooCommerce hosting guide can address performance and scaling separately from DNS.

Staging Domain Protected from Indexing

Use a hostname such as staging.example.com, then:

• Add the required DNS record.
• Map the hostname to the staging application.
• Protect the site with authentication where possible.
• Add a noindex directive.
• Avoid linking publicly to the staging domain.
• Remove or redirect the staging hostname after launch.

Google recommends password protection for private content and states that robots.txt is not a reliable method for preventing a webpage from appearing in search results.

Wildcard Domain Configuration

A       *       CLOUDWAYS_SERVER_IP

Cloudflare documents that wildcard records use * in the hostname field and can be proxied or DNS-only. A wildcard should be added only when the application is designed to process arbitrary subdomains.

Agency DNS Inventory Spreadsheet

Agencies should maintain one row per DNS record with:

• Client
• Domain
• Authoritative DNS provider
• Registrar
• Hostname
• Record type
• Current value
• TTL
• Service owner
• Last verified date
• Change ticket
• Rollback value
• DNSSEC status
• Access owner

This inventory reduces dependency on individual staff members and makes emergency rollback faster.

Which Cloudways DNS Tools Should You Use?

The most useful Cloudways DNS tools are the Cloudways dashboard, authoritative lookup commands, public resolver tools, propagation checkers, and provider-specific DNS consoles. No single tool provides a complete diagnosis, so results should be compared across layers.

Cloudways Domain Management

Use Cloudways Domain Management to:

• Add custom domains
• Select the primary domain
• Add aliases
• View Autonomous target records
• Check “Domain is Live” status
• Access SSL and Cloudflare settings

[Insert image: Show primary and alias domains in Cloudways Domain Management | Alt text: “Manage primary and alias domains in Cloudways”]

Namecheap Advanced DNS

Namecheap DNS records can be edited under Domain List → Manage → Advanced DNS when the domain uses Namecheap BasicDNS, PremiumDNS, or FreeDNS. If third-party nameservers are active, records must be edited at that third party.

[Insert image: Show Namecheap Advanced DNS with root and www records | Alt text: “Point a Namecheap domain to Cloudways”]

GoDaddy DNS Management

GoDaddy allows A-record changes under the domain’s DNS management area when GoDaddy nameservers are authoritative. GoDaddy also warns that changing an existing A record can affect website or email services.

[Insert image: Show the GoDaddy Add A Record form with name, value, and TTL | Alt text: “Point a GoDaddy domain to Cloudways”]

Cloudflare DNS

Use Cloudflare to:

• Review proxy status
• Inspect A, AAAA, and CNAME records
• Control TTL for DNS-only records
• Manage CNAME flattening
• Configure DNSSEC
• Review DNS analytics
• Temporarily bypass proxying

[Insert image: Show Cloudflare DNS records and SSL mode settings | Alt text: “Review Cloudflare DNS and SSL settings for Cloudways”]

dig and nslookup

Use command-line tools to distinguish authoritative data from cached data.

dig +trace example.com
dig A example.com @1.1.1.1
dig AAAA example.com @8.8.8.8
dig CNAME www.example.com
dig MX example.com
dig TXT _dmarc.example.com

nslookup -type=A example.com 1.1.1.1
nslookup -type=MX example.com 8.8.8.8

Free Alternatives

• Google Admin Toolbox Dig
• WhatsMyDNS
• DNSChecker
• Cloudflare DNS lookup tools
• Local terminal commands
• Registrar-provided DNS checks

Propagation websites are useful for regional comparisons, but an authoritative query remains the strongest test of whether the zone itself is correct.

What Should You Do After Connecting Cloudways DNS?

The next step after connecting Cloudways DNS is to verify the complete production path, including domain resolution, SSL, redirects, email, caches, WordPress settings, and search-engine signals. A domain should not be considered launched merely because the homepage opens once.

Post-launch Checklist

• Confirm root-domain resolution.
• Confirm www resolution.
• Test the preferred-domain redirect.
• Test HTTP-to-HTTPS redirection.
• Validate the SSL certificate and hostname coverage.
• Confirm Cloudflare or CDN activation.
• Test email sending and receiving.
• Verify SPF, DKIM, and DMARC.
• Test transactional messages and password resets.
• Test the website from mobile data and another network.
• Check both A and AAAA records.
• Clear Cloudflare, Breeze, Varnish, application, and browser caches.
• Confirm WordPress Address and Site Address.
• Check canonical tags.
• Verify sitemap URLs.
• Inspect robots and noindex directives.
• Add or verify the HTTPS property in Google Search Console.
• Submit the current XML sitemap.
• Monitor uptime and certificate renewal.
• Preserve the DNS inventory and rollback record.

A Cloudways DNS migration should not be considered complete until the domain, SSL certificate, email records, redirects, and authoritative DNS answers have all been verified.

→ Start Your Cloudways Setup

A 30-Minute Launch Monitoring Routine

Immediately after cutover:

1. Query the authoritative A, AAAA, CNAME, MX, and TXT records.
2. Test the homepage and important landing pages.
3. Submit a form.
4. Complete a test login or checkout.
5. Send inbound and outbound email.
6. Check SSL and redirects.
7. Review Cloudways and Cloudflare logs.
8. Repeat from a second network.

Continue monitoring until the previous TTL window has passed.

Conclusion: How Should You Complete a Cloudways DNS Launch?

A reliable Cloudways DNS launch depends on identifying the Cloudways product, the authoritative DNS provider, and the exact destination record required for each hostname. Once those elements are clear, the remaining work becomes a controlled sequence of inventory, configuration, verification, SSL activation, and post-launch testing.

Cloudways Flexible normally uses A records pointing to the server’s public IP. Cloudways Autonomous uses integrated Cloudflare Enterprise targets. DNS Made Easy offers optional centralized authoritative DNS, while a personal Cloudflare account adds separate proxy and SSL decisions.

Inventory the existing zone before making changes. Preserve email and verification records. Query authoritative DNS instead of relying on one browser. Complete SSL, HTTPS redirects, email testing, canonical checks, and Search Console updates only after the required records resolve correctly.

What Are the Most Common Cloudways DNS Questions?

The most common Cloudways DNS questions focus on nameservers, A records, propagation, Cloudflare, SSL, email continuity, and product-specific domain workflows. The following answers address important edge cases that should be checked during setup.

Does Cloudways Host Domain Registrations?

No. Cloudways states that customers must obtain their domains from a domain registrar. The domain can then be connected to a Cloudways application through DNS.

Can I Use Namecheap DNS with Cloudways?

Yes. Keep Namecheap nameservers active and add the Cloudways A records under Advanced DNS, provided the domain uses Namecheap BasicDNS, PremiumDNS, or FreeDNS.

Can I Use GoDaddy DNS with Cloudways?

Yes. Keep GoDaddy nameservers active and add the Cloudways A record in GoDaddy DNS Management. If another provider’s nameservers are active, edit the records at that provider instead.

Do I Need to Change Nameservers to Use Cloudways Flexible?

No. Cloudways Flexible normally works by changing A records at the existing authoritative DNS provider. Nameserver replacement is needed only when intentionally moving DNS to a provider such as Cloudflare or DNS Made Easy.

Should Cloudways Records Be Proxied Through Cloudflare?

Website A and CNAME records can be proxied after origin verification, but provider-verification CNAMEs should remain DNS-only when Cloudways or another service requires the exact DNS answer. Mail records should not be proxied.

Can I Point Multiple Domains to One Cloudways Application?

Yes. Cloudways allows additional domains to be added as aliases to an application. Select one primary domain and configure redirects and canonical tags to avoid duplicate public versions.

Can Cloudways DNS Changes Affect Email?

Changing a website A record normally does not affect mail when MX and TXT records remain unchanged. Replacing nameservers can break email if the new authoritative zone does not contain the required MX, SPF, DKIM, DMARC, and verification records.

What Is the Fastest Way to Diagnose Cloudways DNS?

Query the authoritative nameserver directly, then compare its result with Cloudflare, Google, or another public recursive resolver. This comparison reveals whether the zone is wrong or a resolver is still serving cached data.

References

Cloudflare. (2026, June 24). DNS records. Cloudflare DNS documentation.

Cloudflare. (2026, April 17). Create a zone apex record. Cloudflare DNS documentation.

Cloudflare. (2026, July 9). Full (strict) SSL/TLS encryption mode. Cloudflare SSL/TLS documentation.

Cloudflare. (2026, April 16). Troubleshooting DNSSEC. Cloudflare DNS documentation.

Cloudflare. (2026, April 16). Verify a domain with CNAME. Cloudflare DNS documentation.

Cloudways. (2025, July 23). How to create an A record. Cloudways Help Center.

Cloudways. (2026, July 7). How do I take my website live from Cloudways? Cloudways Help Center.

Cloudways. (2026, April 9). How to activate the DNS Made Easy add-on. Cloudways Help Center.

Cloudways. (2026, June 15). How to add a domain in Cloudways Autonomous. Cloudways Help Center.

Cloudways. (2026, April 24). How to install a Let’s Encrypt SSL certificate. Cloudways Help Center.

Cloudways. (2026). How to use Cloudflare CDN on Cloudways. Cloudways Help Center.

Cloudways. (2025, September 8). Does Cloudways offer name servers? Cloudways Help Center.

Elastic Email. (2026). How to verify your domain. Elastic Email Help Center.

GoDaddy. (2026). Add or edit an A record. GoDaddy Help Center.

Google. (2025, December 10). Block search indexing with noindex. Google Search Central.

Google. (2026). Set up MX records for Google Workspace. Google Workspace Admin Help.

Microsoft. (2026). External Domain Name System records for Microsoft 365. Microsoft Learn.

Namecheap. (2026). How can I set up an A record for my domain? Namecheap Knowledgebase.

Rackspace Technology. (2026). Set up DNS records for Cloud Office email. Rackspace Documentation.

Masum, A. (2026). Cloudways DNS content planning framework [Unpublished editorial brief].