Skip to content
New issue

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

zlint needs update for latest gTLDs #4446

Closed
alexzorin opened this issue Sep 24, 2019 · 1 comment · Fixed by #4449
Closed

zlint needs update for latest gTLDs #4446

alexzorin opened this issue Sep 24, 2019 · 1 comment · Fixed by #4449

Comments

@alexzorin
Copy link
Contributor

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.

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.

@alexzorin alexzorin changed the title zlint gTLD database is outdated zlint need update for latest gTLDs Sep 24, 2019
@alexzorin alexzorin changed the title zlint need update for latest gTLDs zlint needs update for latest gTLDs Sep 24, 2019
@cpu
Copy link
Contributor

cpu commented Sep 26, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants