The configuration validation for the dynamic dns service is not allowing the zone field to be specified when the server name is not cloudflare even if the protocol field is set to cloudflare.
Example configuration triggering this issue:
service custom {
host-name sub.domain.com
login login
password api_key
protocol cloudflare
server api.cloudflare.com/client/v4
zone domain.com
}Expected behavior:
Configuration is validated and accepted, dynamic dns is functional
Actual behavior:
The following error is returned "zone" option only supported with CloudFlare.
Impact:
This shouldn't cause issues since it's relaxing the configuration validation to permit something that wasn't before. It shouldn't be possible to have a configuration that matches this pattern before this fix, so there should be no impact to existing users.