Initial scan of DNS records - some found then none found?

Are there issues with the DNS scanner we’re unaware of?

Running the diagnostics tool, it returns that records (A, AAAA, MX, etc) were found. However, upon initial setup, the number and values of DNS records are inconsistent and incomplete.

For example, one scan may return 8 records out of 22. Remove the site, add again to rescan, and this time only 4 records are found. Repeat and 12 records are found. Repeat and zero records are found.

It’s the most bizarre thing I’ve seen. Previously initial Cloudflare DNS scans have been flawless but there appears to be a gremlin causing mischief somewhere… just need to nail down where is all.

Suggestions or recommendations welcome.

Nope. It’s a guessing game, as Cloudflare does not have AXFR access to your current DNS provider. It’s done a pretty good job when I add domains, but I always go through and make sure to add any missing entries.

Blockquote Cloudflare does not have AXFR access

Thanks for the reply :slight_smile:

I understand that, and have had to manually add the occasional missing record before for other domains, however it’s bizarre why this time around there are significantly inconsistent record discovery results each time.

In the meantime it appears the only reliable solution is to manually enter all zone records.

Thanks again!

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.