3 ms·
No, the protocol didn't support that when it was first written, and that absence has continued through today. Internet protocols are typically written from the
by floatingatoll 5y ago
No, the protocol didn't support that when it was first written, and that absence has continued through today. Internet protocols are typically written from the standpoint that the transport/protocol layer handles all this for them, so the real question is how DNS-over-HTTPS can help manage that, since there's no hope of altering classical DNS. Unfortunately, the MDN page for it seems incomplete, so I have no idea how browsers typically handle that header, much less how a DNS resolver's "DNS-over-HTTPS" shim library will. It might be possible to use the QoS functions of HTTP2 or HTTP3 to accept the connection with a receive maxlen of 0 and send the 503 Retry-After at that point. This also assumes a client coded to behave in a kind manner rather than in a greedy manner, which is generally not a safe bet when "time is money" is a factor.
- tgsovlerkhgsel 5y ago> no hope of altering classical DNS Does DNS support extensibility? If so, an option could be responding with a fake answer like 0.0.0.0 + some TTL, plus an extension that tells modern clients "hey, this is actually a SERVFAIL but please cache it for the TTL".
- KaiserPro 5y agoDNS is distributed. thats the problem, you can return nonsense but it might be ignored by the legion of other DNS services that are caching your responses. because of this there are lots of settings in most servers to ignore and sanitise shitty responses.