v5.x is coming! Big code changes need lots of testing!

[TomOnTime]

#4414 is a major change to the internals of DNSControl. It needs a lot of extra testing.

There should be no user-visible changes. However, since so many internals have changed, extra testing is needed.

See #4414 for the list of changes.

Extra testing needed!

• BIND: SOA handling has been rewritten to be easier to debug and more reliable. Shouldn't have any user-visible changes but please be on the lookout for problems.
• CLOUDFLAREAPI: CF_WORKER_ROUTES() need extra testing. Internally they were represented sometimes as WORKER_ROUTE and sometimes as CF_WORKER_ROUTE. It's amazing such complex code ever worked. Now we use CF_WORKER_ROUTE exclusively. The changes were core to the worker feature. Pleaes give extra attending and testing.
• IMPORT_TRANSFORM() hasn't changed but related parts have.
• Any provider that implements pseudo-types such as CF_WORKER_ROUTES(), BUNNY_DNS_PZ(), etc.

If you maintain a DNS provider, please give this release extra testing!

I only have automated testing for the following providers. All others are at risk of being broken!

AXFRDDNS_DNSSEC AZURE_DNS AZURE_PRIVATE_DNS BIND CLOUDFLAREAPI CNR
DIGITALOCEAN GANDI_V5 GCLOUD HEDNS MYTHICBEASTS NETNOD NS1 ROUTE53
SAKURACLOUD TRANSIP VERCEL

Provider maintainers! Please run the integration tests on this branch and report back any problems. (This is also an excellent opportunity to add your provider to the automated testing list)

How to test:

Test your configuration:

git clone https://github.com/DNSControl/dnscontrol.git
cd dnscontrol
git checkout release_candidate_v5
go build

This will put a dnscontrol (or dnscontrol.exe) binary in the current directory. Use it to run dnscontrol preview on your existing configuration. Try making changes to your configuration, especially if you use "custom times" such as CF_WORKER_ROUTES(), BUNNY_DNS_PZ(), etc.

Test your provider:

Run the full integration test suite: https://docs.dnscontrol.org/developer-info/integration-tests

NOTE: It requires a "test domain". All DNS records from this domain will be deleted. Please use it on a non-production domain (or zone) only!

[TomOnTime]

P.S. There's a new "cookbook" page explaining how to use the new features: https://github.com/DNSControl/dnscontrol/blob/release_candidate_v5/documentation/developer-info/cookbook.md

[TomOnTime]

The v5 release is on hold until codeberg.org/miekg/dns considers these three PRs. They fix/enhance the dns package in ways that I could work around, but it would be much cleaner if I didn't have to.

• https://codeberg.org/miekg/dns/pulls/915
• https://codeberg.org/miekg/dns/pulls/916
• https://codeberg.org/miekg/dns/pulls/919

If your provider is failing on TXT record tests (especially ones that involve backslashes), you might want until these PRs are merged.

[TomOnTime]

I've updated go.mod so that it uses my fork of codeberg.org/miekg/dns, which has the 3 PRs listed above merged.

I suspect this may break some providers and fix others. Having TXT stored as the raw string (not with backslashes) means that one provider broke... because it was working around the bug! Now that the bug is fixed, that's no longer required.

Please test again and report any problems. If the test that fails has to do with TXT records and backslashes, look for code that works around the old bug.

Thanks everyone! I appreciate the testing!