Skip to content

Update CHANGELOG.md#20

Open
bhillkeyfactor wants to merge 15 commits into
release-2.0from
dnsplugins
Open

Update CHANGELOG.md#20
bhillkeyfactor wants to merge 15 commits into
release-2.0from
dnsplugins

Conversation

@bhillkeyfactor

Copy link
Copy Markdown
Collaborator

No description provided.

bhillkeyfactor and others added 15 commits July 7, 2026 13:21
The framework's ResolveDomainValidator matches configured provider
domain patterns (e.g. *.zone.com) against the certificate/zone name,
not the _acme-challenge record name. Resolving on the raw resolved
record name broke the non-delegated path because the _acme-challenge
prefix fails the one-level wildcard match.

Resolve the validator on the cert domain when no CNAME delegation
exists, and on the resolved terminal target when it does, so both the
direct and cross-zone delegated cases select the correct provider.
Fix validator resolution regression for non-delegated challenges
Add a CNAME Delegation section to docsource/configuration.md describing
why challenge names are delegated to an isolated validation zone, how the
CnameResolver follows a multi-level CNAME chain to its terminus, how the
DNS provider plugin is selected against the resolved target (enabling
cross-provider delegation), the loop/depth safety guards, and private-zone
resolution via DnsVerificationServer. Update the enrollment flow summary
to include the CNAME resolution step.
DNS providers are now standalone, pluggable plugins deployed alongside
the AnyCA Gateway rather than built into this ACME plugin. Remove the
hardcoded "supported DNS providers" lists, per-provider credential/config
tables, RFC 2136 setup, and the obsolete IDnsProvider/DnsProviderFactory
"adding new providers" guidance. Point instead to the Keyfactor
-dnsplugin repositories query as the authoritative source, and document
that providers are configured via the Gateway's Domain Validation
config and resolved per domain (including CNAME-delegated targets).
DNS providers are now separate plugins, so the ACME plugin no longer
needs their SDKs or per-provider config fields. Drop the AWS, Azure,
ARSoft (RFC2136), and Nager.PublicSuffix package references (all unused
in code) and remove the DnsProvider selector plus every per-provider
config entry from the integration manifest. Keep the ACME-level fields,
AccountStoragePath (still used for account storage), and
DnsVerificationServer (used for propagation checks and CNAME resolution).
DnsClient is retained for CNAME delegation and TXT propagation.
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 this pull request may close these issues.

1 participant