what kind of DNS record should I set up?

any?

little trick, just add an A/CNAME/smh record that pointing to any meaningless address

If you are going to redirect all traffic, you can just put an A record for

discord

that points to

192.0.2.0

ok, thanks you

@User 1051733646027014194 https://wally.pics/Q9ZBdxIQWi

its #812577823599755274

there are too many channels

@User can’t do this now 😦

For moderator stuff like this, pinging champs is fine. That rule is there so people don't ping cloudflare employees or champs for support questions

oh

But it's dealt with, if there are any other accounts please let us know

@KlartNET personally I prefer using

100::

as an

AAAA

record. IIRC I can't remember my reasoning behind why I prefer that over the

A

record, but I know I had a reason. ;P

AFAIK doing either of those is the approved parking method. I guess

100::

may be easier to remember. Cloudflare will create the complementary record in any case

Less charaters :p

If I don't care about putting more load on origin servers, isn't disabling the Tiered Cache likely better than having it enabled?

Less origin hits are better for your end-users overall. I think the only downside of Tiered Cache currently is that purging the cache may take a few seconds longer.

WAF docs: > Rate limiting rules are not designed to allow a precise number of requests to reach the origin server. In some situations, there may be a delay (up to a few seconds) between detecting a request and updating internal counters. Due to this delay, excess requests could still reach the origin server before Cloudflare enforces a mitigation action (such as blocking or challenging) in our global network. How bad is this delay generally ? Want to use it to enforce 1 request per 10s, is it realistic for denial of wallet attacks against workers.

WAF rate limiter returning CORS error instead of 429, does anyone know why?

If your particular worker costs you a significant amount of money, I would perhaps try to use something like authentication to make sure people aren’t overtaxing you. If you’re just trying to use the WAF to prevent the regular Worker costs being charged, the WAF will be totally fine.

I suspect the 429 page just doesn't have the CORS headers on it

Because the WAF block page doesn't have CORS headers - you can add them on a Transform Rule if you scope it to when

cf.response.error_type

is equal to `ratelimit`:

Thank you so much ❤️

Yep regular workers costs

but still how bad can it get if the same IP makes 20 concurrent requests in 10ms

@Akhilesh switch back to here from DMs about S3 bucket latency. There's a couple solutions: 1. Check the latency of every bucket region from your Worker S3 endpoint. This is what we do. (In our case it makes more sense, since we care about the latency of the Worker S3 endpoint slightly more than the User S3 endpoint. It also allows us to do an upload test first to ensure the endpoint is functional and measure the "real" latency of a

POST

.) 2. Use Cloudflare's load balancer to pick the S3 endpoint with the lowest latency. https://developers.cloudflare.com/load-balancing/ <- this is probably the easiest 3. If you're really insistent on using AWS S3 (IMO not many reasons to ever use AWS S3 over CF R2), I think you can use Route 53 to pick the closest endpoint. And definitely more options, these are just the first three I thought of.

Wish there were something like CORS rules that would handle all options requests and headers automatically Especially annoying with ratelimiting, because browsers send a preflight request, but scripting tools don’t - allowing scripts to achieve 2x more requests

Also options requests should be cacheable asf