The resolver declared udp/53 and nothing else. Its daemon also listens on tcp/53, which a
resolver is asked over whenever an answer will not fit in a datagram.
So on every converged machine that port is closed, while the service reports itself healthy and the
manifest reads as though the resolver were fully declared. Found while reading what converging the
control-node would close: the preview said tcp/53 dnsmasq WILL CLOSE — no module assigned here declares it, directly under udp/53 dnsmasq declared by dnsmasq.
Issue 136 in miniature — a declaration that covers part of what the service does, with the gap silent
because nothing compares the manifest against the sockets the daemon actually opens.
The resolver declared `udp/53` and nothing else. Its daemon also listens on `tcp/53`, which a
resolver is asked over whenever an answer will not fit in a datagram.
So on every converged machine that port is closed, while the service reports itself healthy and the
manifest reads as though the resolver were fully declared. Found while reading what converging the
control-node would close: the preview said `tcp/53 dnsmasq WILL CLOSE — no module assigned here
declares it`, directly under `udp/53 dnsmasq declared by dnsmasq`.
Issue 136 in miniature — a declaration that covers part of what the service does, with the gap silent
because nothing compares the manifest against the sockets the daemon actually opens.
It declared udp/53 only. The daemon listens on tcp/53 as well, and a resolver is
asked over tcp whenever an answer will not fit in a datagram — so on every
converged machine that port is closed while the service reports itself healthy
and the manifest reads as though the resolver were fully declared.
The same fault as issue 136 in miniature: the declaration covers part of what the
service does, and the gap is silent because nothing compares the two.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The resolver declared
udp/53and nothing else. Its daemon also listens ontcp/53, which aresolver is asked over whenever an answer will not fit in a datagram.
So on every converged machine that port is closed, while the service reports itself healthy and the
manifest reads as though the resolver were fully declared. Found while reading what converging the
control-node would close: the preview said
tcp/53 dnsmasq WILL CLOSE — no module assigned here declares it, directly underudp/53 dnsmasq declared by dnsmasq.Issue 136 in miniature — a declaration that covers part of what the service does, with the gap silent
because nothing compares the manifest against the sockets the daemon actually opens.