mirror of
https://github.com/coredns/coredns.git
synced 2026-10-08 19:45:21 -04:00
45ac7fe659
* plugin/quic: add max_connections directive Brings quic to parity with https and https3, which both already expose max_connections. The server-side plumbing already exists and is already wired up: core/dnsserver/config.go declares MaxQUICConnections *int, and server_quic.go already consumes it (DefaultQUICMaxConnections = 200, gates accepted connections on a semaphore sized from it). It was just never parsed from a Corefile directive for the quic plugin itself, so setting it today fails with "unknown property 'max_connections'". Adds the max_connections case to parseQuic, mirroring https3's exact validation (non-negative integer, 0 disables the limit, duplicate definition rejected) since the two share a config field. #8187 did the same shaped fix for https3 reaching parity with https; this does the equivalent for quic, the one remaining sibling without it. Extends TestQuicSetup with max_connections coverage (valid value, 0, missing arg, non-numeric, negative, duplicate definition, extra arg). Verified it fails without the setup.go change (unknown property error) and passes with it. Signed-off-by: stackedbyaradhya <aradhyaj736@gmail.com> * core/dnsserver: propagate MaxQUICConnections across server block keys Addresses review feedback on this PR: Caddy only runs directive setup for the first key in a server block, and the QUIC server reads MaxQUICConnections from group[0]. propagateConfigParams copies listener-wide settings from the first config in a block to the others, but it did not propagate this field. In a multi-transport block where the quic key isn't first, e.g.: .:53 quic://.:8853 { quic { max_connections 1 } } the value was stored on the first (DNS) config while the QUIC config kept MaxQUICConnections nil, so NewServerQUIC silently fell back to the default limit of 200 instead of the configured one. Adds the propagation line, mirroring the existing MaxHTTPSStreams entry (and its comment) added for the equivalent key-order issue on https. Added TestPropagateConfigParamsMaxQUICConnections, mirroring the existing TestPropagateConfigParamsMaxHTTPSStreams. Verified it fails without the register.go change and passes with it. Signed-off-by: stackedbyaradhya <aradhyaj736@gmail.com> --------- Signed-off-by: stackedbyaradhya <aradhyaj736@gmail.com>
52 lines
1.6 KiB
Markdown
52 lines
1.6 KiB
Markdown
# quic
|
|
|
|
## Name
|
|
|
|
*quic* - configures DNS-over-QUIC (DoQ) server options.
|
|
|
|
## Description
|
|
|
|
The *quic* plugin allows you to configure parameters for the DNS-over-QUIC (DoQ) server to fine-tune the security posture and performance of the server.
|
|
|
|
This plugin can only be used once per quic Server Block.
|
|
|
|
## Syntax
|
|
|
|
```txt
|
|
quic {
|
|
max_streams POSITIVE_INTEGER
|
|
max_connections NON_NEGATIVE_INTEGER
|
|
worker_pool_size POSITIVE_INTEGER
|
|
}
|
|
```
|
|
|
|
* `max_streams` limits the number of concurrent QUIC streams per connection. This helps prevent DoS attacks where an attacker could open many streams on a single connection, exhausting server resources. The default value is 256 if not specified.
|
|
* `max_connections` limits the number of concurrent QUIC connections accepted by the server. The default value is 200 if not specified. Connections above the configured limit are rejected. Set to 0 to disable the CoreDNS connection limit.
|
|
* `worker_pool_size` defines the size of the worker pool for processing QUIC streams across all connections. The default value is 512 if not specified. This limits the total number of concurrent streams that can be processed across all connections.
|
|
|
|
## Examples
|
|
|
|
Enable DNS-over-QUIC with default settings (256 concurrent streams per connection, 200 concurrent connections, 512 worker pool size):
|
|
|
|
```
|
|
quic://.:8853 {
|
|
tls cert.pem key.pem
|
|
quic
|
|
whoami
|
|
}
|
|
```
|
|
|
|
Set custom limits for maximum QUIC streams per connection, maximum connections, and worker pool size:
|
|
|
|
```
|
|
quic://.:8853 {
|
|
tls cert.pem key.pem
|
|
quic {
|
|
max_streams 16
|
|
max_connections 50
|
|
worker_pool_size 65536
|
|
}
|
|
whoami
|
|
}
|
|
```
|