Skip to content

Releases: AdguardTeam/dnsproxy

Release v0.55.0

21 Sep 15:34
Compare
Choose a tag to compare

Changed

  • Updated [email protected] dependency to [email protected].
  • Function upstream.NewResolver has been renamed to upstream.NewUpstreamResolver and now doesn't provide the default value for an empty address.

Release v0.54.0

14 Aug 11:34
Compare
Choose a tag to compare

Changed

Release v0.53.1

09 Aug 11:38
Compare
Choose a tag to compare

Fixed

  • Wrong algorithm for sorting IP addresses.

Release v0.53.0

09 Aug 10:20
Compare
Choose a tag to compare

Removed

  • Go 1.19 support, as it has reached end of life.

Release v0.52.0

18 Jul 16:18
Compare
Choose a tag to compare

Added

  • The ability to set the Server HTTP header for DNS-over-HTTPS protocol via CLI arguments and configuration file (#337).

Changed

Fixed

  • Request retry for stale H3 client connections (#340).

Release v0.51.0

30 Jun 13:02
Compare
Choose a tag to compare

Added

  • The ability to specify the DNS timeout via CLI arguments and configuration file (#333).
  • The ability to set domain-specific fallback servers, like in general and private upstream configurations.

Changed

  • The Fallbacks field of the proxy.Config is now an proxy.UpstreamConfig.
  • Validation policy now restricts usage of empty non-nil upstream configurations for the PrivateRDNSUpstreamConfig, and Fallbacks fields of proxy.Config and will cause an error on call to Start.

Fixed

Release v0.50.2

09 Jun 15:23
Compare
Choose a tag to compare

Fixed

  • DNSCrypt upstream not resetting the client and resolver information on dialing errors.

Release v0.50.1

08 Jun 13:27
Compare
Choose a tag to compare

Fixed

Release v0.50.0

06 Jun 10:04
Compare
Choose a tag to compare

Changed

Removed

Release v0.49.2

01 Jun 15:04
Compare
Choose a tag to compare

Fixed

  • Bug in ECS cache when using custom IP (#329).
  • A few security vulnerabilities potentially leading to cache poisoning.