Should `indieauth-metadata` be discoverable by DNS?

I'm finding (somewhat to my surprise) that some developers ([example](https://github.com/fedidcg/FedCM/issues/240#issuecomment-2121721570)) have an easier time updating their DNS records than adding markup to their websites.

I don't know if this is largely true or not, but because I ran into this twice, it seemed worth investigating further if it would be possible to offer a version of `indieauth-metadata` that could be discovered via DNS (TXT?) records, rather than `` tags.

> Context
>
> In trying to implement this https://indieweb.org/FedCM_for_IndieAuth here https://github.com/fedidcg/FedCM/issues/240,
> I think I can move most of the metadata to DNS, for example https://github.com/fedidcg/FedCM/issues/580
> but if there is a single thing that needs to be a link han it defeats the point (because if you can set up a link
> you can set up many).

No implementation file or test is named. Start by reviewing the linked FedCM discussions and the existing indieauth-metadata discovery behavior, then define whether DNS records can replace the link tag, which metadata they must carry, and how discovery would be verified.

Written by the indexing model from the issue text.