PTR for private ip address does not reply for client with public IP address

[ichantio]

Prerequisites

• [x] I have checked the Wiki and Discussions and found no answer

• [x] I have searched other issues and found no duplicates

• [x] I want to report a bug and not ask a question or ask for help

• [x] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.66

Action

$ dig -x 10.10.28.10 @10.10.100.53

Expected result

$ dig -x 10.10.28.10 @10.10.100.53
10.28.10.10.in-addr.arpa. 43100 IN	PTR	private-test.home.arpa.

Actual result

$ dig -x 10.10.28.10 @10.10.100.53
10.28.10.10.in-addr.arpa. 300	IN	SOA	fake-for-negative-caching.adguard.com. hostmaster.10.28.10.10.in-addr.arpa. 100500 1800 900 604800 86400

Additional information and/or screenshots

Problem

Client with public IP addresses unable to resolved reverse lookup of private IP addresses.

Environment

• Mixed clients with either public or private addresses
• Client with private address can do reverse (PTR) lookup for private IP addresses
• Client with public address CANNOT do reverse (PTR) lookup for private IP addresses
• Forward lookup is fine. Both public and private clients can resolve DNS point to private addresses.

Configuration

• Yes upstream private reverse DNS is setup properly
• Even if I specify [/in-addr.arpa/]192.168.8.8 for upstream, Adguard will still ignore it.

Work around

Currently set the public IP range into private_networks config works but that does not seem to make sense.

Expectation

• It is a valid configuration that network clients can have either private or public address
• At the minimum Adguard should respect the primary upstream configuration for [/in-addr.arpa/]192.168.8.8

[geraistec]

I have exactly the same problem.