What problem are you trying to solve?

In #722, PowerAdmin added FQDN validation for CNAME records, including checks for the top-level domain. However, in experimental networks like DN42, we define and use new top-level domains such as .dn42. This causes PowerAdmin's validation to fail, reporting the error: CNAME target must be a fully qualified domain name (FQDN) with a valid top-level domain.

PowerDNS itself does not enforce such restrictions, so I am currently able to manage my DN42 zone properly using pdnsutil edit-zone.

What would you like implemented?

I fully understand the context and intent behind #722; FQDN verification is absolutely essential. Therefore, I believe it would be unreasonable to offer an option to completely disable either FQDN checks or top-level domain checks.

Perhaps we should allow users to define a list, treating the top-level domains in that list as whitelisted, enabling them to pass verification while preventing unintended content from taking effect or even breaking other systems.

Additional context (optional)

No response