Outbound DNS problem

[9ryex5]

Website URL

https://saxeknife.ryex.uk/

Error Message

Outbound curl from my site suddenly fails with “Could not resolve host: saxeknifediscord.95-rui-silva.workers.dev”.

Other Information

(Cloudflare Worker). It worked until ~24h ago, no config changes. Can you check outbound DNS on my account’s server?

[EuropeanRat]

On InfinityFree domains, curl doesn’t return anything which is intentional

Browser Security System - Features and Limitations

InfinityFree uses a security system on all free hosting accounts to ensure your website is accessed by real web browsers, not bots or automated scripts. While this protects your site from malicious traffic, it can affect certain types of access. How the security system works The system checks that visitors can execute JavaScript and accept cookies: features that all modern web browsers support. This verification happens automatically and most website visitors will never notice it. You may occa…

[9ryex5]

Thanks for the reply, but to clarify, this is not inbound access to my InfinityFree site (curl/wget hitting my domain). The article does not apply.

The problem is outbound DNS from PHP on this account fails for Cloudflare Workers.

From a probe script running on the same host (PHP 8.3.19, curl enabled):

• URL: https://saxeknifediscord.95-rui-silva.workers.dev
• gethostbyname(…) → fails (hostname returned unchanged)
• dns_get_record A and AAAA → none / failed
• curl → errno 6: Could not resolve host: saxeknifediscord.95-rui-silva.workers.dev
• HTTP code 0, no primary IP (never connects)

The Worker is fine from other networks (Cloudflare shows invocations, 0 errors). My site’s normal features work. Only server-side outbound HTTPS to *.workers.dev fails with DNS resolution.

Can you check outbound DNS / resolution of workers.dev (and this hostname) on the server for this account?

[Admin]

The setup you’re describing should just work. Access to external APIs is supported, except for a few specific APIs that are blocked. Those include the Telegram API, but it looks like you’ve found a workaround for this.

However, it looks like there is something going on with the DNS resolvers that’s blocked some domain names, including *.workers.dev, from being accessed.

I’m looking into this to see if I can find out what’s going on here.

[Admin]

I have received a definitive answer from iFastNet about this issue. And I’m sorry to say: this is an intentional block, and it will not be lifted.

I’m not sure what you’re doing on Cloudflare Workers, but another person reporting this issue stated it was to be able to access Telegram’s APIs, which we have blocked deliberately.

And that’s precisely the reason we’re blocking access to Cloudflare’s workers now: it’s primarily being used to bypass the Telegram API stuff to send spam and for other abuse.

If you were using Cloudflare Workers for something else, then I’m sorry that you’ve fallen a victim to this. We don’t like having to apply these kinds of measures but free hosting attracts abuse, and we sometimes need to take drastic action to stop it, which may come at the expense of legitimate use cases.