SOLVED: OPNSense - AdGuard Plugin - Cannot update or ping in OPNSense

Started by manwithastick, November 19, 2024, 08:54:35 PM

Previous topic - Next topic
Hello
I am using mimugmail's AdGuard plugin for DNS (192.168.0.1:53)
I am also using Unbound DNS (192.168.0.1:53530)

I have 192.168.0.1:53530 set as my Upstream DNS servers in AGH.
I have no issues with this setup EXCEPT when trying to check for updates and pinging in OPNSense.

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.7.8 at Tue Nov 19 14:41:48 EST 2024
Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/sets/changelog.txz: Host does not resolve
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/meta.txz: No address record
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/packagesite.pkg: No address record
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/packagesite.txz: No address record
Unable to update repository OPNsense
Updating mimugmail repository catalogue...
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:14:amd64/meta.txz: No address record
repository mimugmail has no meta file, using default settings
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:14:amd64/packagesite.pkg: No address record
pkg: https://opn-repo.routerperformance.net/repo/FreeBSD:14:amd64/packagesite.txz: No address record
Unable to update repository mimugmail
Error updating repositories!

Trying to ping from OPNSense

root@OPNsense:~ # ping pkg.opnsense.org
ping: cannot resolve pkg.opnsense.org: Name does not resolve
root@OPNsense:~ # ping google.com
ping: cannot resolve google.com: Name does not resolve

If I disable AGH and set my listen port back to 53 in Unbound, I can update and ping.

Any ideas of what I might be missing. Appreciate the assistance.


Fixed the issue with adding a DNS Server in System: Settings: General
Updates for OPNSense now work fine while still using AGH for the rest of the clients on the network.


I had 1.1.1.1 & 8.8.8.8 set up in System > Settings > General > DNS Servers (override of ISP DNS obtained from WAN).
Then Unbound was set up to use the System nameservers in Services > Unbound > Query Forwarding (& DNS over TLS).

That seemed sufficient (until I played with AGH).