This article is for publishers on Ezoic's nameserver or Cloudflare integration. It covers how to manage DNS records within the Ezoic dashboard, how to handle common DNS conflicts, and what to expect regarding your DNS settings after integrating via the cloud.

Managing DNS Records

Adding or Editing a DNS Record

1. Log into your Ezoic dashboard and navigate to Settings > DNS.
2. To add a record, click Add DNS Record. To edit an existing record, click the pencil icon next to it.
3. Enter the record details:
   • Type — A, CNAME, MX, TXT, SPF, AAAA, or ALIAS
   • Name — the hostname or subdomain. Use @ to represent the root domain (e.g., example.com)
   • Value — the destination the record points to (e.g., an IP address for A records)
   • TTL — time to live in seconds. If unsure, use 300 (5 minutes)
4. Click Add DNS Record or Edit DNS Record to save.

Uploading Multiple DNS Records

1. In Settings > DNS, click the upload option.
2. Download the sample CSV file from your dashboard and populate it with your DNS records.
3. Click Upload, select your file, preview it, and click Add DNS Record.

Adding a Subdomain

Follow the same process as adding any DNS record. For most subdomains, add an A record where the Name field is the subdomain name (e.g., blog for blog.example.com).

Switching Hosting Providers

If you change hosting companies while on cloud integration:

1. Update all DNS records in your Ezoic dashboard to reflect the new host's IP addresses.

If You Are Integrated via Cloudflare

All DNS changes must be made in the Ezoic dashboard first. Changes will automatically propagate to Cloudflare. Any changes made directly in Cloudflare will be overwritten by Ezoic.

DNS Records Not Matching Your Host's Records

Symptom: Your DNS records in Ezoic don't match what you see at your hosting provider, or your host tells you the site "no longer points to their servers."

Explanation: This is expected behavior. When integrated via nameservers, Ezoic acts as a reverse proxy — DNS records point to Ezoic's servers, which then pull your site from your original host. Your site is still hosted where it always was.

What to do: If your host raises this concern, explain that you are using a reverse proxy. Your Ezoic DNS settings show the IP address from which your site is ultimately drawn. You can screenshot these settings to share with your host if needed. Ensure your Ezoic DNS settings are kept current — if your host changes their server IP, update the records in your Ezoic dashboard accordingly.

Email Not Working After Nameserver Change

Symptom: You cannot send or receive email after pointing your nameservers to Ezoic.

Explanation: Ezoic carries over your existing DNS records during integration, including MX records. Email disruption is usually caused by a MX record that was not correctly imported.

What to do: Compare the MX records in your Ezoic dashboard (Settings > DNS) against those at your hosting provider. Ensure they match exactly, then allow time for propagation.

Conflicting DNS Records

Symptom: Your Ezoic dashboard shows an "Issue with DNS Records" notification, or you receive an error when attempting to enable the Cloudflare app.

Explanation: CNAME records cannot share a hostname with other record types (A, TXT, MX, AAAA). Conflicts most commonly occur when a www subdomain has both an A record and a TXT record, or when multiple A records exist for the same hostname.

How to resolve:

1. In Settings > DNS, identify which records share a conflicting hostname.
2. For www conflicts: change the A record for www to a CNAME record pointing to the root domain (@) instead of the IP address.
3. Delete any TXT or other records sharing the same www hostname that are no longer needed. If the TXT record serves a purpose (e.g., domain verification), recreate it with @ as the hostname instead.
4. If multiple A records are flagged, consolidate them into CNAME records mapped to the root record, and delete the conflicting entries.

Note: The root of a DNS zone (the apex domain) cannot be routed via a CNAME or ALIAS record — this is a DNS standard (RFC) restriction, not an Ezoic limitation.

DNS Changes Not Propagating with Cloudflare

Symptom: DNS changes made in Ezoic are not appearing in Cloudflare, or changes made in Cloudflare are being overwritten.

What to do: Always make DNS changes in the Ezoic dashboard. Ezoic is the authoritative source for DNS when integrated via Cloudflare, and changes made directly in Cloudflare will be overwritten.

My site went down after changing nameservers — what do I do?

Verify that the nameservers were updated at your registrar (not your host), and that there are no typos in the Ezoic nameserver values. Propagation can take up to 24 hours. If the site remains down after that, check for origin errors at How to Fix Origin Errors or contact Ezoic support.

Will changing nameservers affect my email?

In most cases, no. Ezoic preserves your existing DNS records including MX records during integration. If email stops working, compare your MX records in the Ezoic dashboard against those at your host and correct any discrepancies.

Can I still use Cloudflare features if I'm on nameserver integration?

Yes. Publishers on nameserver integration can access Cloudflare features via Ezoic's Cloudflare app. This applies to subdomains (including www) but not the root domain apex due to DNS standards.

How do I know if my DNS changes have propagated?

Use a third-party tool such as dnschecker.org to verify propagation across global DNS servers. Changes to records with a TTL of 300 typically propagate within a few minutes to an hour.

If you need further assistance with updating or adding DNS records to Ezoic, please log in via support.ezoic.com to make use of our dedicated resources for support. We're here to help!