Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

CloudFlare DNS validation error – how to fix

by | Nov 13, 2021

Wondering how to resolve CloudFlare DNS validation error? We can help you.

As part of our Server Management Services, we assist our customers with several CloudFlare queries.

Today, let us see how our Support techs resolve this error.

How to resolve CloudFlare DNS validation error?

Typically, error will look as shown below:

Error 1004: Host Not Configured to Serve Web Traffic


Error 1004: DNS is still propagating

A Code 1004 error while working on the Cloudflare dashboard indicates that Cloudflare was unable to complete a requested action.

Today, let us see the steps followed by our Support techs to resolve it.

DNS Validation Error: invalid or missing name (Code: 9000)

Firstly, verify the SRV record you’re adding has a valid name

Then, the record you are adding cannot proxy through Cloudflare.

Toggle the cloud icon from orange to grey for this to work.

Content for A record is invalid. Must be a valid IPv4 address (Code: 9005)

Firstly, verify the IP address of your origin server is correct, is not a Cloudflare IP and has not recently been changed by your hosting provider

Then, remove any blank spaces before and after the IP address

Next, wait a few minutes and try again

Finally, clear your local cache and/or login to your dashboard from an incognito window

Content for CNAME record is invalid (Code: 9007)

Firstly, check the values of the CNAME record you’re trying to add. A CNAME cannot point to an IP address, it can only point to another hostname

Then, make sure you’re adding the correct details, the name should be “www” and content should be “”.

If you’re using Kajabi, review these setup resources here 32.

Invalid content for an MX record (Code: 9009)

Firstly, try entering up the MX records manually, and not copy paste. You might be copy pasting hidden characters.

Then, check with your email host to make sure you’re using the correct mail server settings for your domain.

You’re entering an IP address, an MX-record contains the host name for the mail server, not an IP address, instead of creating the MX record with the IP address, try creating an A record first.

Invalid DNS record type (Code: 9020)

Firstly, you’re making the change via API and you’re missing some required parameters for the request.

Then, you’re attempting to proxy through port 25. Cloudflare does not proxy on port 25 (SMTP), we simply resolve the DNS.

The correct values of the records depend on your email provider.

Please see the Lite Reading MX Record section of this tip to see how to add these on your Cloudflare dashboard.

To check that the DNS for your mail records are returning correctly through Cloudflare, you can run: dig MX

Invalid TTL. Must be between 120 and 2,147,483,647 seconds, or 1 for automatic (Code: 9021)

Firstly, check to see if there is a space before or after the entries.

If you don’t know the TTL value, enter 1 for automatic.

A CNAME cannot point to an IP address, it can only point to another hostname.

Delete any existing CNAME records with IP addresses and recreate them as A records.

An A record is one that points to an IP address.

Then, you’re using a mobile version of the Cloudflare dashboard. Input validation when adding DNS records using the mobile version is a known issue, our team is aware of and working on it.

If the desktop browser window is narrow enough, on Edge and Chrome it will automatically change to the mobile-optimized view and the same problem as mobile happens.

Invalid or missing data for record (Code: 9036)

Firstly, consider adding your CAA records manually through the UI as opposed to via the API.

Consult the Lite Reading section of this tip for details. .

Then, check your API request and make sure you’re including all the necessary details and that you’re using the correct API key.

You’re not correctly defining each piece of the SRV record in the data object. Read more 16 in the API documentation.

Invalid content for ns record (code: 9037)

You’re trying to add Cloudflare name servers to your DNS records.

The name server records need to be modified at your registrar, not within Cloudflare.

If you are using Cloudflare as your authoritative DNS provider, you don’t need name server records unless you want to delegate parts of your site’s DNS to other authoritative DNS.

If Cloudflare is your only DNS provider, remove the name server records.

Setting your NS records to your Cloudflare nameservers is not allowed as they should be set at your domain registrar.

This DNS record cannot be proxied – click the cloud icon to turn it grey to proceed (Code: 9041)

Firstly, check the value of your entry and make sure it’s entered without any following or leading spaces.

You’re trying to proxy (orange cloud) an Amazon SES DKIM record. Domain Key DNS records do not get proxied, they should remain grey clouded.

You’re trying to proxy a record is not proxiable, like your router IP address or mail record.

By switching it to “Grey Clouded”, Cloudflare will serve the record but the IP address can be exposed.

Invalid CNAME target. You aren’t allowed to use records with partial suffixes (Code: 9059)

A CNAME DNS record pointed to should only be created when you are using a third-party set of name servers and you need to proxy through Cloudflare on a partial setup through a hosting provider, not on a full setup when you are using Cloudflare name servers.

This option was disabled as it creates a self-referencing loop for Cloudflare internal DNS and overloads it with a large number of requests from external resolvers.

priority must be an int between 0 and 65535 (Code: 9104)

Firstly, you’re using a mobile version of the Cloudflare dashboard. Input validation when adding DNS records using the mobile version is a known issue, our team is aware of and working on it.

If the desktop browser window is narrow enough, on Edge and Chrome it will automatically change to the mobile-optimised view and the same problem as mobile happens.

An unknown error occurred storing the billing profile (Code: 1004)

Firstly, the billing information that you enter must match the information from the credit card account exactly, including ccv number.

Then, the card was declined, try another card.

Remove the content of the fields “Address 2”, “Company”, and “VAT Number (optional)”.

You’re using a prepaid credit card, try a post paid card.

You may need to consider using PayPal as your payment method in this instance.

Remove any existing payment methods and then add a working card.

Page Rule validation failed: See messages for details (Code: 1004), need to increase cache timeout.

Firstly, remove any Railgun page rules.

Then, your page rule has a redirect loop.

[Stuck in between? We’d be glad to assist you]


In short, today we saw steps followed by our Support Techs to resolve CloudFlare DNS validation error.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.



Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.