When using BIND to backup records locally how to disable fail on ALIAS

[fkrauthan]

So I've followed a suggestion in the docs to enable the BIND DNSProvider (with nsCount set to 0) to have an actual zone backup file of my DNS changes. However when I for example want to use ALIAS it fails as it says BIND does not support it. Also using URL301 writes into the BIND file (as ;@ IN URL301 https://notam.ca) which is fine. However it keeps wanting to apply that change every time I execute a preview or push instead of saying no changes required. Using PORKBUN_URLFWD has the same issue.

[tlimoncelli]

Sadly the strategy of using BIND for backups doesn't work if you have unsupported record types.

You might want to backup the output of "dnscontrol print-ir" instead. It has other problems (doing a restore is non-obvious, and the format can change without warning).

[fkrauthan]

But URL301 is not supported ether and it still writes it into the BIND file (as comment). So shouldn't it do the same thing for ALIAS as well? I like the idea of having a relative easy readable (per domain) file as an additional safety net making sure things produced the expected output.

Maybe it would be good to have some type of HUMAN provider that produces a similar output to print-ir/BIND but into raw text files for easier consumption (and git diffing).