We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
See https://community.letsencrypt.org/t/lets-encrypt-cant-generate-a-cert-for-a-recently-delegated-tld/102650
Currently, cpa domains cannot be issued because zlint produces a e_dnsname_not_valid_tld error during the signing of the precertificate.
cpa
e_dnsname_not_valid_tld
Since Boulder already does a check with publicsuffix-go, perhaps it might be worth disabling the DNSNameValidTLD linter?
DNSNameValidTLD
OTOH stacking linters might be desirable, so maybe just keeping the gTLD database up to date is better.
The text was updated successfully, but these errors were encountered:
Thanks for flagging this @alexzorin. I'll pull in an updated zlint with next week's release and make sure it happens with future TLD map updates.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
See https://community.letsencrypt.org/t/lets-encrypt-cant-generate-a-cert-for-a-recently-delegated-tld/102650
Currently,
cpa
domains cannot be issued because zlint produces ae_dnsname_not_valid_tld
error during the signing of the precertificate.Since Boulder already does a check with publicsuffix-go, perhaps it might be worth disabling the
DNSNameValidTLD
linter?OTOH stacking linters might be desirable, so maybe just keeping the gTLD database up to date is better.
The text was updated successfully, but these errors were encountered: