Cloudflare API ratelimiting

Follow

blaine

July 05, 2016 14:47

In the last week I've started to receive notice regarding ratelimiting to the Cloudflare API for ddns updates.

CloudFlare response for 'sol':
--------------------
err More than 1200 requests per 300 seconds reached. Please wait and consider throttling your request speed (10100)
--------------------

I would imagine this error is indicating Cloudflare is ratelimiting the host OpenDNS making the request from, since my request goes to their endpoint, then they send out to the various services for me.

There were no setting changes on my end prior to the error.

thanks for your help.

1

• 

  rotblitz July 05, 2016 16:40

  You're certainly right.  However, to get more timely attention from OpenDNS, you'll want to open a support ticket, tab "Submit a request" above.  OpenDNS staff must contact CloudFlare to sort it out.  You also can report it to CouldFlare if you like.

  Your best bet as a workaround is to not go through DNS-O-Matic until the issue is being solved, but to update CloudFlare directly.

  0

  Comment actions Permalink
• 

  blaine July 05, 2016 16:52

  Cool, thanks rotblitz.  Request submitted.

  0

  Comment actions Permalink
• 

  xyzulu July 11, 2016 04:44

  I've been in touch with Cloudflare about this.. and they say they are in discussions with DNS-O-Matic (OpenDNS). It seems this is an issue Cloudflare would need to solve on their end however..

  Part of me wonders if Cloudflare support might just end up being dropped by DNS-O-Matic (OpenDNS).

  0

  Comment actions Permalink
• 

  rhaver September 07, 2017 16:06

  This seems to be a problem again. Support request has been submitted. 

  0

  Comment actions Permalink
• 

  rotblitz September 07, 2017 18:39

  Pretty clear what's going on here: CloudFlare sees thousands of update requests coming from the DNS-O-Matic server, for all DNS-O-Matic users using the CloudFlare service.  The problem is with the wrong thinking of CloudFlare: they must measure the update requests by CloudFlare account, not by the server IP address raising them. :(

  Therefore best is you raise the issue with CloudFlare, not with OpenDNS.

  0

  Comment actions Permalink
• 

  angeloscha March 21, 2018 10:45

  Got the same problem just last week. Any solution?

   

  0

  Comment actions Permalink
• 

  rotblitz March 21, 2018 15:23

  See https://support.opendns.com/hc/en-us/community/posts/360001275206

  0

  Comment actions Permalink
• 

  angeloscha March 21, 2018 19:24

  Thanks not relevant I think. I do not use the client neither is same issue.

  Thanks anyway

  0

  Comment actions Permalink
• 

  rotblitz March 21, 2018 21:40

  But you use DNS-O-Matic, do you?

  0

  Comment actions Permalink
• 

  angeloscha March 21, 2018 21:58

  Yes I do. DNS-O-Matic to Cloudflare

  worked like a charm for sometime until few days back..

  0

  Comment actions Permalink
• 

  rotblitz March 22, 2018 14:47 (Edited March 22, 2018 14:51)

  Fine, then this was exactly the problem I linked to and is relevant.  And in case of CloudFlare it is also the issue reported here in the thread.  Two things came successfully together now.

  The DNS-O-Matic problem has been announced to be resolved three days ago.  If you still have problems, I suggest you open a support ticket with OpenDNS, "Submit a request" above, and also a support ticket with CloudFlare.  You certainly understand that the user community cannot help in such cases.

  0

  Comment actions Permalink
• 

  angeloscha March 23, 2018 10:42

  Thanks I did it..

  waiting for response .

   

  0

  Comment actions Permalink

Please sign in to leave a comment.