Are you having issues? If they only have A records, it should just send the request over IPv4. If they have AAAA records but don't support IPv6 whitelisting that would be really silly on their part, but Cloudflare's normal CDN always prefers IPv4 over IPv6 so it may still work -- would have to test that though
#Force workers to only use IPv4 addressess?
sinful crystal
On my quick test it looks like if there is both A/AAAA records for a domain it'll prefer A/IPv4 just like the normal Cdn
keep in mind though if they are using Cloudflare the IP won't be on /ips/, it'l be always 2a06:98c0:3600::103 for subrequests/fetch from Workers
woeful roost
Are you having issues? If they only have A records, it should just send the requ...
Haven't done long term testing (since we don't rely on it if itll be flaky). We're investigating if we need to deploy code somewhere else or if we can keep it at cloudflare.
They do not have AAAA records. It sounds like we shouldn't need to worry about randomly using IPv6 then?
sinful crystal
Unless they're using Cloudflare yea, not possible for it to connect over IPv6 without AAAA records
woeful roost
Actually, calling nslookup returns api.namecheap.com.cdn.cloudflare.net which sounds like namecheap uses cloudflare.
So would it always be 2a06:98c0:3600::103 in that case?