Support proxying wildcard records #2786
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Supersedes #2354
Cloudflare provider doesn't allow proxied DNS records if the records contains wildcard (*) as part of the hostname, irrespective of the zone's plan. A while ago, Cloudflare announced availability of wildcard proxy in all tiers
This PR updates the
shouldBeProxied
validation, so that it no longer skips wildcard record when checking for proxied statusOther Changes
Fixes #1810
Relates #1542
Fixes #ISSUE
Checklist