2 ms·
The DoH server needs to be identified using a URL (a target for POST requests) or template (for GET requests). There isn’t a standard way to get from a server n
by fanf2 7y ago
The DoH server needs to be identified using a URL (a target for POST requests) or template (for GET requests). There isn’t a standard way to get from a server name to a DoH URL and DoH servers differ in their choice of path name.
- jlgaddis 7y agoWe pretty much already have this exact thing with options 66 (hostname) and 67 (filename) for clients booting via TFTP. Most DoH servers, AIUI, use the same well-known path, so we'd simply need two more DHCP options: one for the DoH server's hostname and another for the path. There's no reason something like this couldn't easily be added to the DHCP specification and, at some point, I expect it will... everyone will come together to agree on the details and we'll end up with a new/updated RFC.