On each attempt to connect to a federated instance:
1) check presence of TLSA record in DNS for _xxx._tcp.host.example.com where _xxx is the target port number used by Mastodon/Matrix
2) get the hash from the TLSA record
3) when TLS connection is established, verify the TLSA hash against the certificate actually received
Details https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities
For me, it sounds really strange that you got that reaction. It sounds like the next logical step to take for synapse!
Also, I would love if the @nextcloud client would support it aswell!
@kravietz @selea Can you elaborate on what you want from that feature and how you imagine it working?