Reverse RFC1918 local use zones unexpected behaviour

Hi,

I have 4 identical configured Unbound, and for 2 local configured stub for 10.in-addr.arpa subzone work as I expected, 2 not.
System is CentOS Linux release 7.4.1708 (Core) and Unbound 1.4.20 from base repo. Some details:

$ rpm -qa | grep unbound
unbound-1.4.20-34.el7.x86_64
unbound-libs-1.4.20-34.el7.x86_64

$ unbound-control status
version: 1.4.20
verbosity: 1
threads: 2
modules: 2 [ validator iterator ]
uptime: 961903 seconds
unbound (pid 7495) is running…

/etc/unbound/unbound.conf

private-address: 10.0.0.0/8
local-zone: “2.10.in-addr.arpa.” transparent
stub-zone:
name: 2.10.in-addr.arpa
stub-addr: 192.168.96.96

On first two Unbound query results is expected:

$ dig -x 10.2.40.50 @192.168.6.6

; <<>> DiG 9.10.5 <<>> -x 10.2.40.50 @192.168.6.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39411
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;50.40.2.10.in-addr.arpa. IN PTR

;; ANSWER SECTION:
50.40.2.10.in-addr.arpa. 300 IN PTR server1.internal.company.com.

;; Query time: 0 msec
;; SERVER: 192.168.6.6#53(192.168.6.6)
;; WHEN: Fri Dec 15 18:32:09 Central Europe Standard Time 2017
;; MSG SIZE rcvd: 88

$ dig -x 10.10.10.10 @192.168.6.6

; <<>> DiG 9.10.5 <<>> -x 10.10.10.10 @192.168.6.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31411
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;10.10.10.10.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
10.in-addr.arpa. 10800 IN SOA localhost. nobody.invalid. 1 3600 1200 604800 10800

;; Query time: 0 msec
;; SERVER: 192.168.6.6#53(192.168.6.6)
;; WHEN: Fri Dec 15 18:36:48 Central Europe Standard Time 2017
;; MSG SIZE rcvd: 112

But on second two query results is wrong:

$ dig -x 10.2.40.50 @192.168.9.9

; <<>> DiG 9.10.5 <<>> -x 10.2.40.50 @192.168.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22389
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;50.40.2.10.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
10.in-addr.arpa. 10800 IN SOA localhost. nobody.invalid. 1 3600 1200 604800 10800

;; Query time: 0 msec
;; SERVER: 192.168.9.9#53(192.168.9.9)
;; WHEN: Fri Dec 15 18:42:02 Central Europe Standard Time 2017
;; MSG SIZE rcvd: 111

$ dig -x 10.10.10.10 @192.168.9.9

; <<>> DiG 9.10.5 <<>> -x 10.10.10.10 @192.168.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15000
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;10.10.10.10.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
10.in-addr.arpa. 10800 IN SOA localhost. nobody.invalid. 1 3600 1200 604800 10800

;; Query time: 0 msec
;; SERVER: 192.168.9.9#53(192.168.9.9)
;; WHEN: Fri Dec 15 18:42:14 Central Europe Standard Time 2017
;; MSG SIZE rcvd: 112

For last 2 queries log is empty on verbosity 3.

Any idea, suggestions?

Regards,

--
Mehmed Kahric