fix hitting flood protection

[br4nnigan]

you could probably get the exact value for flood protection from the first reponse but I dont know how as I'm not proficient in python and this works too

[fetzerch]

Can you please give #11 a try? The server indeed contains the number of seconds to wait in every response.

[br4nnigan]

I tested it and actually I'm not so sure anymore if the flood protection has been the problem in the first place (I dont remember specifically). The flood protection isn't a problem anymore anyway.

The problem I identified now is that certbot pulls an outdated txt record. This occurs almost randomly, I added a delay like in my original pull request in suspicion that the certbot checks the record before the change is live. Sometimes I would even get a success at 1s delay, I increased it to 3, 5, 10. I'm still getting an error in half the cases. Now 10s is high enough to verify myself that the change is live while the script is sleeping and before certbot checks and it still failed, which is odd.

Now these delays to wait for propagation of the dns record seem to be essential, for example the "official" authenticator plugin for cloudflare uses a default of 10 seconds. But even at 30 (!) seconds I can't reliably get a success.

Creating a cron job to renew certs seems out of question as it must be reliable.