Release v0.68.0

Added

• The field proxy.Config.PrivateSubnets used to determine if the address of a client or the address requested via PTR is considered private. The netutil.IsLocallyServed is used by default.
• The field proxy.Config.UsePrivateRDNS controls if the requests considered private should be resolved via proxy.Config.PrivateRDNSUpstreamConfig. Such requests answered with NXDOMAIN otherwise.
• The field proxy.DNSContext.IsPrivateClient which determines if the client's address is considered private.
• The field proxy.DNSContext.RequestedPrivateRDNS containing the prefix parsed from a requested ARPA domain, if the request itself is PTR for a private address and came from a private client.
• The proxy.ValidatePrivateConfig function to validate if an proxy.UpstreamConfig may be used for private RDNS.

Changed

• PTR requests for domains containing DNS64 prefixes are now answered with NXDOMAIN if proxy.Config.UseDNS64 is set to true, but proxy.Config.UsePrivateRDNS is not.
• Fallback servers aren't used for the aforementioned requests, as well as for all private RDNS requests.
• All the private RDNS requests coming from external (non-private) client are now answered with NXDOMAIN before proxy.RequestHandler.
• proxy.New now requires proxy.Config.PrivateRDNSUpstreamConfig to be valid as per proxy.ValidatePrivateConfig if proxy.Config.UsePrivateRDNS is set to true.

Docker

• Updated golang image to 1.22.2

---

Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.68.0

Release v0.67.0

Added

• The new proxy.Config.MessageConstructor field of the new proxy.MessageConstructor type that is used to build DNS messages. The default legacy implementation is used in case of nil.

Changed

• The proxy.UpstreamConfig.SubdomainExclusions field type is now *container.MapSet.

Warning

Previously released v0.66.1 has been removed as it contains breaking changes.

---
Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.67.0

Release v0.66.0

Added

• The new proxy.New constructor for proxy.Proxy structure.

Changed

• The proxy.Proxy.Start method now accepts a context.
• The proxy.Proxy.Stop method has been renamed to proxy.Proxy.Shutdown and now accepts a context.

Deprecated

• The proxy.Proxy.Init method. Use proxy.New instead.

---
Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.66.0

Release v0.65.2

Fixed

• The upstream.CachingResolver caching algorithm, which removed certain resource records within an RR set (AdguardTeam/AdGuardHome#6723).

Important

Release v0.65.1 hasn't been released. This release only differs from v0.65.1 in testing code.

---
Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.65.2

Release v0.65.0

Changed

• The minimal Go version has been changed to Go 1.21.7.
• The quic-go library has been updated.

Docker

• dnsproxy is now built with Go 1.21.7

---

Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.65.0

Release v0.64.1

Fixed

• Parsing of the IPv6 upstreams without a port number (#379).

---

Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.64.1

Release v0.64.0

Added

• The new proxy.ParseError error which contains an index of the line of the upstream list.

Changed

• proxy.ParseUpstreamsConfig is now returns wrapped error containing proxy.ParseError. It also skips empty lines and comments.

---
Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.64.0

Release v0.63.1

Changed

• Improved DNS-over-QUIC concurrent work (#373).
• Improved logging.

---

Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.63.1

Release v0.63.0

Changed

• proxy.Config.TrustedProxies field's type is now netutil.SubnetSet instead of []string.

---
Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.63.0

Release v0.62.0

Added

• The new upstream.CachingResolver implementation of the upstream.Resolver interface. It's used to account the TTL of resolved addresses and resolve those on demand.
• The new upstream.NewCachingResolver function to wrap the upstream.UpstreamResolvers.

Changed

• Upstreams are now bootstrapped on each call of Exchange, meaning that caching the lookup results is now the Options.Bootstrap resolver's responsibility.

---
Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.62.0