I use FreeDNS, aka FreeDNS to connect back to the Sophos SG UTM I setup for my parents. Since my parents are provided a dynamic IP from their ISP, using FreeDNS in connection with the Sophos UTM has been a solid way for me to remotely access the UTM despite their IP changing on a regular basis.
When I attempted to connect to the subdomain, i.e., subdomain.chickenkiller.com, as provided by FreeDNS, using the CloudFlare Malware Filtering DNS, aka 126.96.36.199, the domain was blocked from resolving.
When I attempted to connect to the domain using regular, unfiltered CloudFlare DNS, aka 188.8.131.52, I was able to reach the dynamic subdomain/UTM without an issue.
I know the Malware Filtering DNS is new for CloudFlare, is this the intended behavior? My parents are currently using OpenDNS in conjunction with the Sophos SG UTM to provide them with a secondary internet filter. I was intending to switch them to CloudFlare DNS with malware filtering from OpenDNS, but this obviously would be a deal breaker. This unfortunately also prevents me from using 184.108.40.206 for malware filtering on my own network.
I need to know if this new behavior is in the intended behavior for dynamic DNS services with the new CloudFlare Malware filtering DNS or if this is another bug with 220.127.116.11 for families being new?