Afraid's Dynamic DNS domains just stopped resolving

[robbiedees]

Hi,
Starting within the last hour or two, DNS lookups to 1.1.1.3 and 1.0.0.3 began failing to return results for Afraid.org's Dynamic DNS domains. This has worked fine for years, and just began failing.

Example
nslookup mooo.com 1.1.1.3
Server: UnKnown
Address: 1.1.1.3

Non-authoritative answer:
Name: mooo.com
Addresses: ::
0.0.0.0

But all other DNS resolvers are fine, even

nslookup mooo.com. 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: mooo.com
Addresses: 70.39.97.227
169.47.130.85

[robbiedees]

These lookups are still failing nearly 24 hours later, so this doesn’t seem to be a temporary issue.

What is the issue?

[Chaika]

@robbiedees

mooo.com

mooo.com is categorized as “pornography” and “Adult Themes” on Cloudflare Radar
https://radar.cloudflare.com/domains/domain/mooo.com
You can submit categorization feedback via the link on there.

1.1.1.3 is Cloudflare for Families, so that’s why it is blocking it.

1.1.1.1 → blocks nothing
1.1.1.2 → Blocks Malware
1.1.1.3 → Blocks Malware & Adult Content
Docs: https://developers.cloudflare.com/1.1.1.1/setup/

Edit: I didn’t realize it because of the name, but mooo.com is one of the default Dynamic DNS Domains for FreeDNS? Cloudflare is treating all subdomains of it as the same domain since it isn’t part of the Public Suffix List, and it looks like one user ruined it for everyone else.

[robbiedees]

Thanks for the information on the “Cloudflare Radar” - have not seen that information before!

How would you submit that that the current categories are incorrect? or not applicable to all subdomains? Categorizing a root domain is not good for anyone…