Encountering DNS conflicts when using Cloudflare via Ezoic's Name Server integration can be a common hurdle for publishers. This article aims to address the DNS issues that arise, particularly when attempting to use the Cloudflare app on subdomains. We'll cover the typical conflicts, such as those involving multiple DNS records with the same hostname, and provide clear, actionable steps to resolve these issues. By following this guide, you'll ensure seamless integration and optimal performance for your site. Let's dive into the troubleshooting process to get your DNS settings configured correctly.

Users experiencing Cloudflare DNS errors commonly encounter the following symptoms:

1. DNS Conflicts: Alerts such as "Issue with DNS Records" appearing in the Ezoic dashboard.
2. Record Incompatibility: Errors indicating the need to change an "m" record from an A record to a CNAME record, but being unable to do so due to multiple records with the same hostname (e.g., "A, TXT").
3. Error Related to Specific Subdomains: Conflicts caused by specific subdomains having multiple DNS records mapped to the same IP address.
4. CNAME Record Issues: Errors showing violations when trying to map all traffic to the root domain for the DNS zone if there are existing conflicting records (e.g., “m” TXT record).
5. Multiple A records: Alerts about multiple A records being flagged that need consolidation into CNAME records mapped to the root record.

Cloudflare DNS errors

When your site is integrated via Name Servers you can also utilize the Cloudflare app via Ezoic’s account. This can only be done for all subdomains of the domain and not the root***.


There are often DNS conflicts that occur and these will show in your Ezoic dashboard 

"Issue with DNS Records. The Cloudflare app requires changing your DNS \"m\" record from an A record to a CNAME record. However, it is unable to do so because you have multiple records with that hostname of types \"A, TXT\". If you would like to use Cloudflare for your site, please delete the other records"

Below you can see the two records for the domain example.com the two records are mapped to the same IP address.

This error is usually related to the specific subdomain in question causing a conflict, usually if there is another record such as a TXT record that shares the same hostname. In the example above that means that the TXT record also was set to use the “m” hostname.

In order to fix this issue, the A record can usually be changed to a CNAME record that is mapped to the root domain for the DNS zone. This essentially says “all traffic to go to X” as seen below.

It will be a violation to also have an existing DNS record for that entry as well, in the above case the “m” TXT record. If the record was kept it would cause conflicts and so, this can subsequently be deleted, and if there isn't already an existing one, added as an exact replica with the hostname as @ as seen below.

If there are multiple violations where multiple A records are flagged, they can all be consolidated into CNAME records that are mapped to the root record, and the corresponding conflict records deleted providing the respective record exists for the root of the DNS zone.

Additional info:

***Currently we are unable to route the apex of a DNS zone via an ALIAS or CNAME record as this violates RFC which is a document that describes the standards, protocols, and technologies of the Internet and TCP/IP.

To prevent DNS conflicts and maintain optimal performance when using Cloudflare via Ezoic’s account, consider the following tips:

1. Regularly Monitor DNS Records: Frequently check your DNS records within the Ezoic dashboard to promptly identify and resolve any conflicts.
2. Consolidate DNS Records: Whenever possible, consolidate multiple DNS records into CNAME records that are mapped to the root domain. This reduces the complexity and potential for conflicts.
3. Avoid Duplicate Hostnames: Ensure that no two DNS records share the same hostname, especially avoiding the overlap of A and TXT records with the same hostname.
4. Adhere to DNS Standards: Follow the standards outlined in RFC documents to avoid violations that can cause conflicts or disruptions. Specifically, do not attempt to route the apex of a DNS zone via an ALIAS or CNAME record.
5. Update Records Promptly: When changes are needed, such as converting an A record to a CNAME record, make sure to delete conflicting records immediately to prevent issues.

By implementing these tips, you can reduce the likelihood of DNS conflicts and ensure smoother integration with Cloudflare via Ezoic’s account.

If you need further assistance with conflicting Cloudflare DNS records, please log in via https://support.ezoic.com/ to make use of our dedicated resources for support. We're here to help!