I have this little zone file
testing.it 8600 IN SOA dns.testing.it. hostmaster.testing.it. 2026010900 86400 1800 604800 600
@ IN NS dns.testing.it.
@ IN A 127.0.0.1
dns.testing.it IN A 127.0.0.1
@ IN TXT "This character can't be signed è" --> (note the special character è)
When i try to sign this file with the default policy the pipeline is stopped for an error corresponding to the special character
cascade zone status
Status report for zone 'testing.it' using policy 'default'
✔ Waited for a new version of the testing.it zone
• Loading ..
Loaded 213 B and parsed 0 records in 9 seconds
x An error occurred that prevents further processing of this zone version:
x Encountered an error while loading the zone: The record could not be parsed: 6:44: bad symbol
After modify the TXT RR with
@ IN TXT "This record can be signed"
The file it's signed and published
Status report for zone 'testing.it' using policy 'default'
✔ Waited for a new version of the testing.it zone
✔ Loaded version 2026010900
Loaded at 2026-01-09T22:12:15+00:00 (8s ago)
Loaded 206 B and 5 records from the filesystem in 0 seconds
✔ Auto approving signing of version 2026010900, no checks enabled in policy.
✔ Approval received to sign version 2026010900, signing requested
✔ Signed version 2026010900 as version 2026010901
Signing requested at 2026-01-09T22:12:19+00:00 (4s ago)
Signing started at 2026-01-09T22:12:20+00:00 (3s ago)
Signing finished at 2026-01-09T22:12:20+00:00 (3s ago)
Collected 5 records in 0s, sorted in 0s
Generated 2 NSEC(3) records in 0s
Generated 7 signatures in 0s (7 sig/s)
Inserted signatures in 0s (7 sig/s)
Took 1s in total, using 2 threads
Current action: Finished
✔ Auto approving publication of version 2026010901, no checks enabled in policy.
✔ Published version 2026010901
Published zone available on 127.0.0.1:4543
I had the same results with à è ì ò ù. This characters are encoded in UTF-8.
I have this little zone file
testing.it 8600 IN SOA dns.testing.it. hostmaster.testing.it. 2026010900 86400 1800 604800 600
@ IN NS dns.testing.it.
@ IN A 127.0.0.1
dns.testing.it IN A 127.0.0.1
@ IN TXT "This character can't be signed è" --> (note the special character è)
When i try to sign this file with the default policy the pipeline is stopped for an error corresponding to the special character
cascade zone status
Status report for zone 'testing.it' using policy 'default'
✔ Waited for a new version of the testing.it zone
• Loading ..
Loaded 213 B and parsed 0 records in 9 seconds
x An error occurred that prevents further processing of this zone version:
x Encountered an error while loading the zone: The record could not be parsed: 6:44: bad symbol
After modify the TXT RR with
@ IN TXT "This record can be signed"
The file it's signed and published
Status report for zone 'testing.it' using policy 'default'
✔ Waited for a new version of the testing.it zone
✔ Loaded version 2026010900
Loaded at 2026-01-09T22:12:15+00:00 (8s ago)
Loaded 206 B and 5 records from the filesystem in 0 seconds
✔ Auto approving signing of version 2026010900, no checks enabled in policy.
✔ Approval received to sign version 2026010900, signing requested
✔ Signed version 2026010900 as version 2026010901
Signing requested at 2026-01-09T22:12:19+00:00 (4s ago)
Signing started at 2026-01-09T22:12:20+00:00 (3s ago)
Signing finished at 2026-01-09T22:12:20+00:00 (3s ago)
Collected 5 records in 0s, sorted in 0s
Generated 2 NSEC(3) records in 0s
Generated 7 signatures in 0s (7 sig/s)
Inserted signatures in 0s (7 sig/s)
Took 1s in total, using 2 threads
Current action: Finished
✔ Auto approving publication of version 2026010901, no checks enabled in policy.
✔ Published version 2026010901
Published zone available on 127.0.0.1:4543
I had the same results with à è ì ò ù. This characters are encoded in UTF-8.