4 ms·
And why not just use the DNS server itself for this? Like negotiate with the DNS if it supports DoH? Why does it need to influence other standards like DHCP? I
by numlock86 7y ago
And why not just use the DNS server itself for this? Like negotiate with the DNS if it supports DoH? Why does it need to influence other standards like DHCP?
It's the same with deal with HTTP and HTTPS basically: The server tells me if HTTPS is supported or not. (Yes, there is HSTS but that's a different story ...)
- jlgaddis 7y agoThe first thing that comes to mind is that DHCP option 6 specifices (one or more) IP addresses, whereas with DoH you probably want to specify (ideally, multiple) hostnames, for various reasons.
- fanf2 7y agoThe 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.