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
To use DNS01 validation with an RFC-2136 compliant nameserver, a secret holding the TSIG key has to be created (see: https://cert-manager.io/docs/configuration/acme/dns01/rfc2136/#configuration-step-2---set-up-cert-manager). Further, a check like the acme-dns check should be added using nsupdate (see: https://cert-manager.io/docs/configuration/acme/dns01/rfc2136/#using-nsupdate).
nsupdate
Not providing full integration for DNS validation using RFC-2136 in this component
The text was updated successfully, but these errors were encountered:
RFC-2136 should be possible:
solvers: sec_dns01: dns01: rfc2136: nameserver: ns.example.com tsigKeyName: cert_manager_key tsigAlgorithm: HMACSHA512 tsigSecretSecretRef: name: cert-manager-rfc2136 key: tsig-key selector: dnsZones: - 'example.com'
Sorry, something went wrong.
No branches or pull requests
Context
To use DNS01 validation with an RFC-2136 compliant nameserver, a secret holding the TSIG key has to be created (see: https://cert-manager.io/docs/configuration/acme/dns01/rfc2136/#configuration-step-2---set-up-cert-manager).
Further, a check like the acme-dns check should be added using
nsupdate
(see: https://cert-manager.io/docs/configuration/acme/dns01/rfc2136/#using-nsupdate).Alternatives
Not providing full integration for DNS validation using RFC-2136 in this component
The text was updated successfully, but these errors were encountered: