Remi Gacogne via dnsdist:
thanks for the pointer, really looking forward to the dnsdist version
that has this solved.
Sure, I expect to release 1.9.2 including this fix in the next couple
weeks.
thanks!
Note that this metric (doh_http_version_queries) is incremented after
doing some
Hi,
On 18/03/2024 22:00, Christoph via dnsdist wrote:
This might be related:https://github.com/PowerDNS/pdns/issues/13850,
not backported yet
thanks for the pointer, really looking forward to the dnsdist version
that has this solved.
Sure, I expect to release 1.9.2 including this fix in the
Otto Moerbeek wrote:
This might be related:https://github.com/PowerDNS/pdns/issues/13850,
not backported yet
thanks for the pointer, really looking forward to the dnsdist version
that has this solved.
Remi wrote:
In addition to the issue mentioned by Otto, it might also be that the
Hi Christoph,
In addition to the issue mentioned by Otto, it might also be that the
monitoring does not support HTTP/2. The new nghttp2 provider for
incoming DNS over HTTPS does not support HTTP/1.1. In 1.9.x it's still
possible to switch back to the legacy h2o provider but note that it will
On Sun, Mar 17, 2024 at 06:41:13PM +0100, Christoph via dnsdist wrote:
> Hi,
>
> in February we upgraded our test DoH/DoT server from 1.8.3 to 1.9.0
> but we did not notice any problems so we upgraded our production server
> from 1.8.3 to 1.9.0 yesterday.
>
> Immediately after upgrading our
Hi,
in February we upgraded our test DoH/DoT server from 1.8.3 to 1.9.0
but we did not notice any problems so we upgraded our production server
from 1.8.3 to 1.9.0 yesterday.
Immediately after upgrading our monitoring claimed our DoH service is
unavailable (HTTP 400) but we were unable to
