Closed sudheesh001 closed 4 years ago
I don't think this is necessary. If the KeyId is wrong, the target will fail to decrypt the query, and inform the client as such (with a generic error). Plus, with DNSSEC and a reliable transport like DoH used for fetching the key, malformed records are unlikely to arise.
The current discovery of the designated DoH servers mentions the retrieval of the public key from the DoH server as the
odohkey
in the HTTPSSVC DNS record. The client retrieves a DNSSEC signed record and validates it. Additionally, it'd make sense to also have a hash of the odohkey available as theodohkey-id
in the records so that the client can perform a check forodohkey.KeyID() == odohkey-id
in addition to ensuring that these are DNSSEC signed records?