3 ms·
The main problem with this is that you need to handle TCP connections, in which the queries do not have to match up to packet boundaries, and the client can mul
by fanf2 6y ago
The main problem with this is that you need to handle TCP connections, in which the queries do not have to match up to packet boundaries, and the client can multiplex internal and external queries on the same connection.
The interface for DNS from an arbitrary container is the DNS protocol, and since you can’t control the software that is making the queries on the client side of the protocol, you have to do the special logic on the server side.
- ptomato 6y agoDo you, realistically? The standard behavior for most things afaik on looking up a domain name is to send out an A query and (simultaneously ideally) A queries with searchdomains appended. That's not gonna get anywhere near 512 bytes for a fly .internal service name, I'd expect.
- fanf2 6y agoThe requirement is to support arbitrary containers, so it should still work if the container contains stub resolver software that pipelines requests over TCP.