Yes, @Cloudflare, what’s going on with these changes? We actually still have multiple locations with IpV4 as the identifier that were added prior to your recent changes, and they still work great. However, adding new locations is no longer an option and provides the following message while using both Free and Pro plans:
“Free plan accounts cannot have more than one location with IPv4 enabled.”
Lol - I’ve tried reaching out them both on a paid (Pro) and the Free plan, and no answer! Cloudflare is not known for their stellar customer support, as we all know. This is also a major function in Cloudflare, so I’m surprised that we’re not seeing more users reporting on this issue…
I could never get any chat or email support on this, so I gave up and moved to a different service provider. Pretty disappointing as I’ve been a long-time Cloudflare customer.
I already had configured 3 location for my free account for a few years already and now I try just to change the default DNS location and I get the same error “Free plan accounts cannot have more than one location with IPv4 enabled.”. Even trying to update the IP address (via a refresh option to autodetect the IP address from which I connect to the dashboard) is no longer possible.
As I read it, it seems the limitation is listed as 250 on the mentioned link Account limits, with more available for the Enterprise plans, unless I am mistaken.
You are in the same boat as the rest of us! I’ve even upgraded to Pro and got the same results with only 3 locations added. What really makes me frustrated is that Cloudflare hasn’t even taken a minute to clear this up with us, despite the numerous complaints!
With IPv4 addresses no longer available in the free plan, I found a workaround by using DoH to still benefit from DNS policies.
I’ve set up a cloudflared daemon to proxy upstream DNS queries to the unique DoH URL listed on the DNS Locations page. My local DNS server forwards queries to this daemon, which listens on a specified port. This setup successfully enforces all configured policies, effectively blocking sites as intended.
The only drawback is that if DNSSEC is enabled on your local DNS server, blocked sites might take a bit longer to time out, rather than being instantly blocked or overridden.
I thought about that workaround myself, but then I have to deal with another component in the query chain, which introduces latency and complexity. So frustrating that Cloudflare can’t answer what specific plan we need to be on to reap benefit from this feature NATIVELY these days!