DNS rewrites don't generate corresponding PTR record for IP addresses

anaander commented 2 years ago

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

Operating system type

Linux, Other (please mention the version in the description)

CPU architecture

AMD64

Installation

Docker

Setup

On one machine

AdGuard Home version

v0.107.11

Description

What did you do?

Created a DNS rewrite for a local IP address and hostname

Expected result

In addition to an A record, a PTR record would be created to allow reverse lookups.

Actual result

No PTR record is created, lookups only work in one direction (lookup of hostname works, lookup of IP fails)

Screenshots (if applicable)

Additional information

PTR records are a vital part of network infrastructure validation and should be a part of any modern DNS configuration.

ainar-g commented 2 years ago

Hello. It is currently recommended to use the dnsrewrite rules instead of the rewrites on the Filters → DNS rewrites page. You can add PTR records with these as well.

The DNS rewrites feature should have a massive redo in the v0.108 cycle, and we'll include this when planning it. Thanks.

inventorematto commented 2 years ago

Hello Guys! Same need here! Since i've moved all my local DNS entries from /etc/hosts (mapped file on docker container) to the "dns rewrite" page im not able to lookup anymore.

Query LOG ptr1