PTR lookup returns NXDomain if upstream DNS answers to fast

[TheB1gG]

Hello,
this is just a sanity check and if somebody can reproduce this it should be turned into a bug report I guess.
My setup is Adguard Home -> Adguard Home -> Ubiquiti USG-3
PTR lookup returns NXDomain if upstream DNS answers to fast log https://gist.github.com/TheB1gG/a1df1e733ab3cacfb37ac61140fbe1b3
With this I get the correct PTR from Adguard

22:50:16.739784 enp1s0f0 Out IP 192.168.2.2.34348 > 192.168.2.1.53: 1539+ [1au] PTR? 86.2.168.192.in-addr.arpa. (66)
22:50:16.739784 enp1s0f0 Out IP 192.168.2.2.38960 > 192.168.2.1.53: 1539+ [1au] PTR? 86.2.168.192.in-addr.arpa. (66)
22:50:16.739785 enp1s0f0 Out IP 192.168.2.2.54854 > 192.168.2.1.53: 1539+ [1au] PTR? 86.2.168.192.in-addr.arpa. (66)
22:50:16.740586 enp1s0f0 In  IP 192.168.2.1.53 > 192.168.2.2.34348: 1539* 1/0/1 PTR Family-Room.main.internal. (93)
22:50:16.740946 enp1s0f0 In  IP 192.168.2.1.53 > 192.168.2.2.38960: 1539* 1/0/1 PTR Family-Room.main.internal. (93)
22:50:16.741365 enp1s0f0 In  IP 192.168.2.1.53 > 192.168.2.2.54854: 1539* 1/0/1 PTR Family-Room.main.internal. (93)

With this I get NXDomain

22:50:19.696258 enp1s0f0 Out IP 192.168.2.2.55662 > 192.168.2.1.53: 45518+ PTR? 86.2.168.192.in-addr.arpa. (43)
22:50:19.696880 enp1s0f0 In  IP 192.168.2.1.53 > 192.168.2.2.55662: 45518* 1/0/0 PTR Family-Room.main.internal. (82)
22:50:20.736093 enp1s0f0 Out IP 192.168.2.2.34214 > 192.168.2.1.53: 51347+ [1au] PTR? 86.2.168.192.in-addr.arpa. (66)
22:50:20.736093 enp1s0f0 Out IP 192.168.2.2.37794 > 192.168.2.1.53: 51347+ [1au] PTR? 86.2.168.192.in-addr.arpa. (66)
22:50:20.736837 enp1s0f0 In  IP 192.168.2.1.53 > 192.168.2.2.34214: 51347* 1/0/1 PTR Family-Room.main.internal. (93)
22:50:20.737249 enp1s0f0 In  IP 192.168.2.1.53 > 192.168.2.2.37794: 51347* 1/0/1 PTR Family-Room.main.internal. (93)