-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Description
Prerequisites
-
I have checked the Wiki and Discussions and found no answer
-
I have searched other issues and found no duplicates
-
I want to report a bug and not ask a question or ask for help
-
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)
FreeBSD, AMD64 (aka x86_64)
Installation
Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)
Setup
On a router, DHCP is handled by the router
AdGuard Home version
v0.107.56
Action
Replace the following command with the one you're calling or a
description of the failing action:
nslookup 192.168.1.100
Server: Firewall
Address: 192.168.1.1
*** 192.168.1.100 wurde von Firewall nicht gefunden: Non-existent domain.Expected result
The appropriate hostname of the client
Actual result
nslookup 192.168.1.100
Server: Firewall
Address: 192.168.1.1
*** 192.168.1.100 wurde von Firewall nicht gefunden: Non-existent domain.
Additional information and/or screenshots
Adguard home on OpnSense 25.1-amd64, FreeBSD 14.2
I cannot define a reverse DNS Server via Web-UI. everytime I want to save the config i get the following error without saving:
I have to remove the server on "inverse dns section" and uncheck the "private reserve" option. BTW: Is "inverse dns" the same like "reverse DNS"?
I defined the setting via yaml config file, but doesn't work either:
private_networks: []
use_private_ptr_resolvers: true
local_ptr_upstreams:
- 192.168.1.1
The private_networksdoesn't work either.
Similar topics I found:
#6928
https://github.com/AdguardTeam/AdGuardHome/wiki/Configuration#specifying-upstreams-for-reverse-dns
#4476

