Hi Andreas,
The suggestion is implemented in the commit
https://github.com/NLnetLabs/unbound/commit/114edf2c3819dc2bb02784c7ba3f9776aa8cde3b
That prints the warning if the 'quic-port' setting is used but
dnsoverquic was not enabled when compiled.
Best regards, Wouter
On 10/12/24 23:16, A. Schulze via Unbound-users wrote:
Am 11.10.24 um 08:54 schrieb Wouter Wijngaards via Unbound-users:
It is fixed in
https://github.com/NLnetLabs/unbound/commit/1b7e14dc39256b172a93412e23a60cde86a7548c
Hello Wouter,
I confirm, the error no longer occur. But...
As said, I've build with '--without-libngtcp2'
now I could write:
unbound.conf:
server:
do-daemonize: no
logfile: ""
do-ip6: no
interface: 0.0.0.0@853
quic-port:853
Shouldn't this raise an error as quic is unavailable? Instead, unbound
serve Do53 on Port 853 with this configuration.
It's the same for any other port.
I think, if compiled with '--without-libngtcp2' the configuration option
'quic-port' should raise a similar warning as doqclient:
root@5fa727139f4e:/# doqclient
Compiled without ngtcp2 for QUIC, cannot run doqclient.
I also tried to compile with '--without-libnghttp2' If I now add
'https-port: 443' unbound warn:
[1728767572] unbound[26:0] warning: Unbound is not compiled with
nghttp2. This is required to use DNS-over-HTTPS.
same should happen for "quic-port" ...
Andreas
