Releases: AdguardTeam/dnsproxy
Releases · AdguardTeam/dnsproxy
Release v0.45.1
Fixed
- A few race conditions in DNS-over-HTTPS upstream code (#279).
Release v0.45.0
Added
-
DNS-over-HTTP/3 support for the upstreams. Run
dnsproxy
with--http3
flag to enable DoH3 automatic support. In this casednsproxy
will choose automatically between HTTP/2 and HTTP/3 depending on which probe connection was faster. Alternatively, you can specifyh3://
scheme to force HTTP/3. -
DNS-over-HTTP/3 support for the server-side. Run
dnsproxy
with--http3
flag to enable DoH3 support. In this case it will listen for both DoH2 and DoH3 requests. -
Added 0-RTT support to the DoQ upstream implementation.
Changed
- Several general stability improvements in the DoQ upstream.
Release v0.44.0
Changed
- DNS-over-QUIC connections now use keepalive.
Removed
- Go 1.17 support.
Release v0.43.1
Fixed
- ID mismatch errors in QUIC (#239; thanks, @Lanius-collaris!).
Release v0.43.0
Added
-
Backwards-compatible support of the final DNS-over-QUIC RFC 9250.
-
Field
proxy.DNSContext.DoQVersion
. -
Type
proxy.DoQVersion
and the corresponding constants. -
The
DoQCode*
constants in packagesproxy
andupstream
.
Changed
- Field
proxy.DNSContext.QUICSession
has been renamed toproxy.DNSContext.QUICConnection
.
Release v0.42.4
Fixed
- Priority of the selection of upstreams for domains when a wildcard is used.
Release v0.42.3
Added
- The new
*.example.com
notation, allowing users to specify and upstream for all subdomains of a domain, but not the domain itself. - Fields
proxy.UpstreamConfig.SpecifiedDomainUpstreams
andproxy.UpstreamConfig.SubdomainExclusions
.
Release v0.42.2
Fixed
- Occasional leaks of TCP connections.
Release v0.42.1
Changed
- Better detection of special-purpose IP addresses.
Release v0.42.0
Changed
- The default DNS-over-QUIC port is now
853
instead of754
.
Removed
- Previously deprecated upstream DNS server URL scheme
dns://
.