How to filter out LAN / private addresses resolution?

[macruspareto]

Running the latest 2.0.45 on Windows.

In my dnscrypt access/nx logs I'm noticing tons of requests for PTR regarding intranet / non-routable private addresses.

127.0.0.1 255.1.168.192.in-addr.arpa PTR SYNTH 2ms -
127.0.0.1 255.1.168.192.in-addr.arpa PTR SYNTH 0ms -
127.0.0.1 178.1.0.224.in-addr.arpa PTR NXDOMAIN 656ms cs-rome
127.0.0.1 178.1.0.224.in-addr.arpa PTR NXDOMAIN 943ms cs-milan
127.0.0.1 5.1.168.192.in-addr.arpa PTR SYNTH 2ms -
127.0.0.1 5.1.168.192.in-addr.arpa PTR SYNTH 1ms -

Is there an option to bounce any PTR requests for all internal addresses like 224.0.* or 192.168.* (because this doesn't make any sense and puts unnecessary strain on remote DNS servers).

[jedisct1]

SYNTH means that the response was locally synthesized. PTR queries for local addresses are never sent to upstream resolvers; there's nothing to configure, dnscrypt-proxy does it out of the box.

224.0.* is not a set of internal addresses. With the exception of 224.0.0.*, everything here is routable to the Internet.

224.0.1.1 for example, has a PTR record:

 drill PTR 1.1.0.224.in-addr.arpa.

;; ANSWER SECTION:
1.1.0.224.in-addr.arpa.	28633	IN	PTR	ntp.mcast.net.

If you really want to block something, you can add it to your block list, like any zone.

[flesler]

I have the opposite question, is it possible to have PTR queries be properly resolved by letting it go upstream?