dnsdist 1.9 not working but dnsdist 1.7 working

[dhs26206]

Hello everyone !!

During configuring dnsdist on Debian 13 which has latest 1.9.0 version , Its not working as it worked before when configuring with same conf file on Debian 12 with version 1.7.3

On both fresh VMs I tried same config

You can see below :

setSecurityPollSuffix("")
setKey("abcd") -- for console access (required)

addDOHLocal("127.0.0.1:5353", nil, nil, "/dns-query", { reusePort=true })

newServer({address="1.1.1.1", healthCheckMode='lazy', checkInterval=60, lazyHealthCheckFailedInterval=30, rise=2, maxCheckFailures=3, lazyHealthCheckThreshold=20, lazyHealthCheckSampleSize=50, lazyHealthCheckMinSampleCount=10, lazyHealthCheckMode='TimeoutOnly'})

Command : curl -v -H 'accept: application/dns-json' "http://127.0.0.1:5353/dns-query?name=google.com&type=A"

When doing curl on dnsdist 1.9.0 the response is

• Trying 127.0.0.1:5353...
• Connected to 127.0.0.1 (127.0.0.1) port 5353
• using HTTP/1.x

GET /dns-query?name=google.com&type=A HTTP/1.1
Host: 127.0.0.1:5353
User-Agent: curl/8.14.1
accept: application/dns-json

• Request completely sent off
• Received HTTP/0.9 when not allowed
• closing connection #0
  curl: (1) Received HTTP/0.9 when not allowed

When doing curl on dnsdist 1.7.3 the response is

• Trying 127.0.0.1:5353...
• Connected to 127.0.0.1 (127.0.0.1) port 5353 (#0)

GET /dns-query?name=google.com&type=A HTTP/1.1
Host: 127.0.0.1:5353
User-Agent: curl/7.88.1
accept: application/dns-json

< HTTP/1.1 400 Bad Request
< Date: Sat, 27 Dec 2025 18:58:03 GMT
< Connection: keep-alive
< Content-Length: 32
< Server: h2o/dnsdist
< content-type: text/plain; charset=utf-8
<

• Connection #0 to host 127.0.0.1 left intact
  Unable to find the DNS parameter

Tell me how to do it properly on this new version ??

[rgacogne]

1.7.3 is using the h2o library while 1.9.0 defaults to using nghttp2, which does not support HTTP/1.1. I would suggest using HTTP/2 instead of 1.1. If you really want to support 1.1 you can set the library parameter of addDOHLocal to h2o, but please be aware that h2o is no longer maintained in a way making it usable as a library (no releases, API is not stable) so its use in dnsdist has been deprecated and will be removed. Le 27 décembre 2025 19:16:59 UTC, DDKS ***@***.***> a écrit :

…

Hello everyone !! During configuring dnsdist on Debian 13 which has latest 1.9.0 version , Its not working as it worked before when configuring with same conf file on Debian 12 with version 1.7.3 On both fresh VMs I tried same config You can see below : setSecurityPollSuffix("") setKey("abcd") -- for console access (required) addDOHLocal("127.0.0.1:5353", nil, nil, "/dns-query", { reusePort=true }) newServer({address="1.1.1.1", healthCheckMode='lazy', checkInterval=60, lazyHealthCheckFailedInterval=30, rise=2, maxCheckFailures=3, lazyHealthCheckThreshold=20, lazyHealthCheckSampleSize=50, lazyHealthCheckMinSampleCount=10, lazyHealthCheckMode='TimeoutOnly'}) Command : curl -v -H 'accept: application/dns-json' "http://127.0.0.1:5353/dns-query?name=google.com&type=A" When doing curl on dnsdist 1.9.0 the response is * Trying 127.0.0.1:5353... * Connected to 127.0.0.1 (127.0.0.1) port 5353 * using HTTP/1.x > GET /dns-query?name=google.com&type=A HTTP/1.1 > Host: 127.0.0.1:5353 > User-Agent: curl/8.14.1 > accept: application/dns-json > * Request completely sent off * Received HTTP/0.9 when not allowed * closing connection #0 curl: (1) Received HTTP/0.9 when not allowed When doing curl on dnsdist 1.7.3 the response is * Trying 127.0.0.1:5353... * Connected to 127.0.0.1 (127.0.0.1) port 5353 (#0) > GET /dns-query?name=google.com&type=A HTTP/1.1 > Host: 127.0.0.1:5353 > User-Agent: curl/7.88.1 > accept: application/dns-json > < HTTP/1.1 400 Bad Request < Date: Sat, 27 Dec 2025 18:58:03 GMT < Connection: keep-alive < Content-Length: 32 < Server: h2o/dnsdist < content-type: text/plain; charset=utf-8 < * Connection #0 to host 127.0.0.1 left intact Unable to find the DNS parameter Tell me how to do it properly on this new version ?? -- Reply to this email directly or view it on GitHub: #16681 You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[dhs26206]

Ohh !!

Actually, in my case, dnsdist was between nginx and pihole to enable DoH, unfortunaltely neither I want to remove nginx from 443 nor nginx proxy supports HTTP/2

Chatgpt is suggesting nghttpx or envoy in between , but they are complex for this case.

Need to find something !!

Anyways Thanks for clarification ,
My unproductive hours came to an end !!