Automatic DNS Update incorrectly setting TLSA records (only 3 1 1, 2 1 1 are missing)

Issue Description

When using automatic DNS Management only the 3 1 1 entries for each endpoint are set, the 2 1 1 are missing

Expected Behavior

I expected that both records are set

Actual Behavior

only 3 1 1 is set

Reproduction Steps

  1. Configure Automatic DNS Management with RFC 2136
  2. Update the TLSA records

Relevant Log Output

Failed to create DNS record for _995._tcp.mx01.example.net.: Failed to create DNS record: Response error: RR Set should not exist; Failed to create DNS record for _443._tcp.mx01.example.net.: Failed to create DNS record: Response error: RR Set should not exist; Failed to create DNS record for _993._tcp.mx01.example.net.: Failed to create DNS record: Response error: RR Set should not exist; Failed to create DNS record for _465._tcp.mx01.example.net.: Failed to create DNS record: Response error: RR Set should not exist; Failed to create DNS record for _25._tcp.mx01.example.net.: Failed to create DNS record: Response error: RR Set should not exist

Stalwart Version

v0.16.x

Installation Method

Binary (Linux)

Database Backend

RocksDB

Blob Storage

Filesystem

Search Engine

Internal

Directory Backend

OIDC

Additional Context

BOth records have the same name. I assume the record is update in two steps, instead of in one transaction containing both values.

I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.

on

I have searched this support forum (open and closed topics) and confirm this is not a duplicate.

on

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

This will be fixed in v0.16.7.