DNS records quick scan
To help all customers get started when a new zone is created, Cloudflare offers a DNS records quick scan.
How the quick scan works
The scan is built upon a list of recurring patterns of DNS records
name, that Cloudflare identifies as being used in existing active zones.
Since DNS record names are automatically appended with the domain that the records are set for, two completely different domains -
test.xyz, for example - would probably have a few matches if the lists of DNS records on their zones were compared side by side and the criterion was
The DNS records
content would be different for each zone but, based on record
name, Cloudflare can identify recurring patterns and expect to find the same pairs when a new domain is added.
The following section provides some examples of DNS records
name combinations that the scan usually finds.
Use case examples
@ indicates the domain apex - in the example above,
Since it is still common that visitors type
www.<DOMAIN> in their browsers expecting to reach the domain, zones will usually have a or an record named
www. This allows queries for
www.<DOMAIN> to return the expected result.
Mail exchanger (
MX) and other record types combined with names like
smtp, are also commonly found. As explained in the , there are several DNS records that can be used to make sure email reaches your mail server and to prevent other email senders from spoofing your domain.
Since the DNS records quick scan is based on this predefined list of commonly used record types and names, and is not tailored to the specific zone you are adding to Cloudflare, there can be cases where not all records are picked up.
For example, if you have very specific hostnames - such as
my-store1900.example.com instead of
store.example.com - or if you have set up a that uses a more custom name -
this._domainkey instead of
default._domainkey - it is expected that the scan will not find the specific DNS records.