Hi, I am very new to OPNsense (recently moved over from OpenWrt) and I'm enjoying the upgrade very much ;D
I have an existing instance of AdGuard Home already running on a separate server in my network.
I was able to configure OPNsense to use my existing instance of AdGuard (
not as a plugin) and everything works well, with one exception:
AdGuard does not see the hostnames in its dashboard.I was hoping that someone may be able to point what I'm doing wrong, please:
AdGuard Home version: v0.107.38 (latest)DNS Settings:
- Upstream DNS servers: 127.0.0.1:53 & 127.0.0.1:8053
- Parallel requests: Yes
- Fallback DNS servers: None
- Private reverse DNS servers: Gateway_IP
- Use private reverse DNS resolvers: Checked
- Enable reverse resolving of clients' IP addresses: Checked
DHCP Server: Disabled in AdGuard (I am using the DHCPv4 from OPNsense; IPv6 is disabled across the network)
OPNsense version: 23.7.5 (latest)System\Settings\General:
- DNS servers: ADGUARD_IP | Use gateway: No
- DNS search domain: None
- Allow DNS server list to be overridden by DHCP/PPP on WAN: Unchecked
- Do not use the local DNS service as a nameserver for this system:: Checked
- Allow default gateway switching: Unchecked
Services:
- Dnsmasq DNS: Enabled: No
- OpenDNS: Enabled: No
- Unbound DNS: Enabled: No
OPNsense FIrewall rules (NAT):
(https://bit.ly/3rHs5Db)
OPNsense Firewall rules (ALL_LOCAL) - which represents my local and trusted VLANs:
(https://bit.ly/3LQGaF8)
Despite all devices having a hostname by default, I also provide it in OPNsense's DHCP lease for static clients, yet AdGuard does not see any of it:
(https://bit.ly/3twqHne)
Any thoughts on how to get the client hostnames from OPNsense to also propagate over to AdGuard?
A few options are, HW capabilities dependent in some instances, I'd recommend a).
- Go for b) if HW constraints don't allow running AGH on the FW
a) Move AGH to OPNsense
b) Move DHCP to AGH
c) Do static mappings in AGH - Filters - DNS rewrites
reverse dns is working fine here.
have you checked if something is wrong with your adguard settings or blocked by firewall itself?
https://github.com/AdguardTeam/AdGuardHome/wiki/Configuration#specifying-upstreams-for-reverse-dns
Quote from: newsense on October 09, 2023, 03:00:51 AM
a) Move AGH to OPNsense
b) Move DHCP to AGH
c) Do static mappings in AGH - Filters - DNS rewrites
a) Separate AGH seems to be more stable than the OPNsense plugin - I saw on this forum many people had issues recently because of updates to either OPNsense/AGH/AGH plugin on OPNsense - thankfully I never had any of those issues, plus I can easily backup/rollback AGH with no impact on OPNsense
b) I don't want to depend on AdGuard for anything more than adblocking. I like the idea that I can just replace AGH with say Pihole or something else and have close to zero impact on OPNsense.
c) This is what I currently do... and it gets very tedious after a while, especially when working with many devices and containers
Quote from: marunjar on October 09, 2023, 09:09:02 AM
reverse dns is working fine here.
have you checked if something is wrong with your adguard settings or blocked by firewall itself?
https://github.com/AdguardTeam/AdGuardHome/wiki/Configuration#specifying-upstreams-for-reverse-dns
Did you have to partake in some sort of black magic rituals to get this working, because I want in as well ;D
I added the following to my upstream DNS servers in AGH
[/in-addr.arpa/]192.168.101.1
[/ip6.arpa/]192.168.101.1
127.0.0.1:53
127.0.0.1:8053And then 192.168.101.1 as the Private reverse DNS server.
For reference - AdGuard is running in VLAN_101 and its IP address is 192.168.101.12, and the gateway IP of that VLAN is 192.168.101.1> nslookup 192.168.101.134
** server can't find 134.101.168.192.in-addr.arpa: SERVFAIL
> nslookup homeassistant.lan
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: homeassistant.lan
Address: 192.168.101.134
> ping homeassistant.lan
PING homeassistant.lan (192.168.101.134) 56(84) bytes of data.
64 bytes from 192.168.101.134: icmp_seq=1 ttl=64 time=0.672 ms
64 bytes from 192.168.101.134: icmp_seq=2 ttl=64 time=0.517 ms
--- homeassistant.lan ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 12015ms
rtt min/avg/max/mdev = 0.467/0.572/0.672/0.083 ms
> ping 192.168.101.134
PING 192.168.101.134 (192.168.101.134) 56(84) bytes of data.
64 bytes from 192.168.101.134: icmp_seq=1 ttl=64 time=0.678 ms
64 bytes from 192.168.101.134: icmp_seq=2 ttl=64 time=0.662 ms
--- 192.168.101.134 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5101ms
rtt min/avg/max/mdev = 0.561/0.700/0.965/0.127 ms
Sorry for my intrusion in the post.
i have installed AGH on OPNsense but no see client name
this my config:
DHCP on OPNsense with static lease and this the gateway
LAN 192.168.1.254
VLAN10 192.168.10.254
VLAN20 192.168.20.254
disable unbound dns on OPNsense
on AGH use the standaard cfg and when i add upstream dns (127.0.0.1 / 192.168.1.254) i recive the error on AHG