dns-capacity verifiedWritten by the Hub
Lookups in flight
in the configuration this is a line
dns-capacity: 128How many DNS operations may be outstanding at once.
Values
- Values
positive integer- Default
128 · taken from the build- applying
restart required- where it can be set
in the config file · with a startup flag · as an environment variable
In detail
The resolver is asynchronous, so this is the width of its pipeline rather than a thread count. 128 against a documented 100 — another small difference between the pages and the package. The console's "DNS operations" widget shows started, completed and queued counts, which is where this limit becomes visible: a queue that never empties means the pipeline is too narrow for the sending rate, or the resolver is too slow.