Closed Nuhvi closed 6 months ago
Depressingly, this seems to work, which means I dropped the ball with the relay API.
The reason the relay API is <signature><timestamp><packet>
is because the first two are known size, so no need to deserialize the packet first, however, I could have written the size of the packet at the end of the response.
Tested with dig
and curl
Closing as this seems to offer little value over GET endpoint in the relay spec, and it is not specced so I can't confirm it will work with all clients.
Is there a way to format the
SignedPacket
serialization so that old DNS clients may consume the encoded packet and ignore/tolerate the timestamp and signature? If so, then relays and DoH DNS servers can become the same thing.