Cloudflare adds 200 random records when adding a domain

[jpuser]

My question seems the same as this, which was not resolved.

When adding new domain, cloudflare adds 200 random records

Hi, we got this problem recently. When adding new domains(recent 3 or 4) to cloudflare, when scans it adds 200 random records. All domains comes from same provider. (ns1.serveriai.lt etc) It was not a problem before. The problem is: it should not be added. The second problem is to remove those 200 records one by one. It is time consuming.

I just added a domain with 4 DNS records, but Cloudflare somewhat added 200 random records. I don’t have any wildcard records as the server does not support it. This looks like there’s been an ongoing bug with Cloudflare DNS setup procedures.

[jpuser]

I’d prefer to hide it from public. Is there a way to share this directory with CF staffs?

[jpuser]

I found a temporary solution, which is to delete the domain and add again as described in here.

2 pages of random A-records detected – has anyone seen this before?

Not sure why that would be if the setup is the same on other domains you have added. Maybe someone else here has seen it before.

[jpuser]

Here’s another related topic for reference.

68 Random DNS records added

I’ve only seen random DNS records added because there’s a wildcard DNS entry at the host, so when Cloudflare starts guessing at possible subdomain hostnames, they all resolve.

[jpuser]

For any future users who may face this trouble, here’s the soluion.

Keep deleting and adding again and again until CF scan’s the correct DNS records.

For the domain in trouble, I repeated 3 times, and finally CF scan was able to properly handle 4 existing records.

[domjh]

Can you email [email protected] from your account email with the details and the domain this happened for. When you get an autoresponse please post the ticket number here.

[fritex]

Some possible workaround ideas:

DNS: why too much record?

I wish there is one … unfortunately, not yet possible and we might have to wait for this feature to be available. Some ideas and possible workarounds: Similar feature requests:

[CascadingStyle]

The scanning tool is the best effort attempt at identifying existing DNS records, and whether it works is entirely dependent on your current Authoritative DNS provider’s response to DNS queries.

Even if you did not create the records, the existing or former Nameserver provider responded to those queries with an IP address or CNAME value.

Let’s say that you never created the FTP subdomain, ftp.example.com, but when we query for this record, the DNS provider responds with an IP of a parked/block/error page. The record would still be added to your DNS settings, this is expected.

Our documentation is getting moved a bit lately, and I’m not finding the article we had in place about DNS Scans, these are some of the references I found:

• Regarding controlling the import: Manage DNS records · Cloudflare DNS docs

If you want more control over which DNS records are imported and how, use the bulk imports .

• Another explanation of the feature: Scan DNS Records - Cloudflare API v4 Documentation

Scan for common DNS records on your domain and automatically add them to your zone. Useful if you haven’t updated your nameservers yet.

• If you would like to mass remove DNS records, the easiest approach would be to use the API:
  1. Retrieve a list of existing DNS records using: List DNS Records - Cloudflare API v4 Documentation
  2. Audit which DNS records you want removed
  3. Delete the DNS records using: Delete DNS Record - Cloudflare API v4 Documentation
  • This can be scripted to remove all the records at once.