CD
Cloudflare Developers•17mo ago
Chaika

You can disable AAAA records for your

You can disable AAAA records for your entire zone by modifying the IPv6 Compatibility Setting via the API (not possible to modify in the dash), but not for specific records on your zone.
5 Replies
Unknown User
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Chaika
Chaika•17mo ago
You wouldn't be able to force back IPv6 on records by manually creating AAAA Records as far as I know, as that setting effects the Proxy IPs Cloudflare responds with, it doesn't care about your actual records Unless of course you made your records unproxied There's no way to turn off IPv4 either, so at best you could have two zones (websites), one with IPv4 (IPv6 disabled), and the other with IPv4/IPv6 (hoping that browsers properly prefer IPv6)
Unknown User
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Chaika
Chaika•17mo ago
I don't think what you're trying to do will be possible without Enterprise, or just using some other public service to get the IPs for you. There was one hosted on Workers (CF was sponsoring it, so presumely Ent and such), I forget the name though It's worth noting though that it doesn't matter what record you use when it is proxied. You could have an A/AAAA, or a CNAME. Cloudflare responds to DNS Queries with A/AAAA with its own IPs. You can use the API to disable the AAAA Records, but yea like you noticed you cannot disable IPv4 Records, so you just have to rely on clients preferring IPv6 by default (which most should, if they have it, especially browsers), and filtering out IPv4 results from the IPv6 endpoint
Unknown User
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Want results from more Discord servers?
Add your server
More Posts
Automatic deployments not working, cannot deploy any changes.Nothing else appears to be out of the ordinary except for the lack of workflow activity on the repo,Delete requests cause 400 without reaching workerWhen using a DELETE request, I am getting 400 responses and the worker is not handling the request. Pages with IPv4 Only (DNS?)I'm trying to run a page that retrieves the user's IPv4 address. It specifically needs to be v4. I'mi m not sure why they aren t the GitHubi'm not sure why they aren't. the GitHub release looks fine - https://github.com/cloudflare/terraforDurable objects would be ok forDurable objects would be ok for matchmaking at a small scale but at larger scale durable objects wilBecause as Kian mentioned the SPA doesBecause as Kian mentioned the SPA does not have a server so the cors approach would never really worI m running into an `AuthenticationI'm running into an `Authentication error [code: 10000]` error when executing `wrangler dev` @ `2.8.Prisma in module workerAnyone have an example of using '@Prisma/client/edge' in a cloudflare module worker? I am getting: env variables get wiped out during deploying changes via cli (i.e. wrangler publish)I noticed that the env variables I have set up for the worker via the dashboard get deleted every tiAPI versioning on workersWhat's the most efficient way to add versioning to our workers API?