Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: robota.us.to
I ran this command:(I am using gitlab so it was an automated thing)
Let’s Encrypt has rate limits to ensure fair usage:
There’s no way for Let’s Encrypt to tell the difference between a personal domain, a corporate domain, a university domain, and a free DNS domain unless the domain owners contact us (or the Public Suffix List) and tell us about their situation. (Let’s Encrypt also doesn’t have the resources to go out and proactively research the policies of all the free DNS providers.) Therefore, free DNS services are subject to the rate limit by default in the same way as any other domain.
Your best options are to get the administrators of the service to request a rate limit exemption, or to switch to a different free DNS provider which has already done this.
Would you please recommend to me a free dns provider that has already done this, or is there a list out there for figuring it out. The dns site I used is a huge one where anonymous people provide free sub domains, so finding a way to contact them would be relatively impossible. Thank you for all of your help, hopefully I can get this working before the competition starts in September.
If you open the list and go down to the “BEGIN PRIVATE DOMAINS” section heading – it’s very far down – you can look through the organizations and domains in the list. Most of them aren’t DNS services, but the ones that are are usually obvious. (The UK Home Office, no. A company with “DNS” in its name and dozens of short domains, probably yes.)
Let’s Encrypt’s rate limit adjustment list isn’t public.
The Public Suffix List maintainers don't appreciate submissions just intended to short-circuit Let's Encrypt rate limits, but the cookie security benefits are very relevant to dynamic DNS services.
The rate limiting documentation schoen linked above mentions it -- you have to fill out this form: