Release v0.68.0
Added
- The field
proxy.Config.PrivateSubnetsused to determine if the address of a client or the address requested via PTR is considered private. Thenetutil.IsLocallyServedis used by default. - The field
proxy.Config.UsePrivateRDNScontrols if the requests considered private should be resolved viaproxy.Config.PrivateRDNSUpstreamConfig. Such requests answered withNXDOMAINotherwise. - The field
proxy.DNSContext.IsPrivateClientwhich determines if the client's address is considered private. - The field
proxy.DNSContext.RequestedPrivateRDNScontaining 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.ValidatePrivateConfigfunction to validate if anproxy.UpstreamConfigmay be used for private RDNS.
Changed
- PTR requests for domains containing DNS64 prefixes are now answered with
NXDOMAINifproxy.Config.UseDNS64is set to true, butproxy.Config.UsePrivateRDNSis 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
NXDOMAINbeforeproxy.RequestHandler. proxy.Newnow requiresproxy.Config.PrivateRDNSUpstreamConfigto be valid as perproxy.ValidatePrivateConfigifproxy.Config.UsePrivateRDNSis set to true.
Docker
- Updated golang image to 1.22.2
Original release: https://github.com/AdguardTeam/dnsproxy/releases/tag/v0.68.0