A way to change the order of plugin startup when booting?

Started by FormBurden, November 01, 2021, 01:25:14 AM

Previous topic - Next topic
Update: Sorry it's been a good while before getting back.

But I finally switched up the order to AdGuard so now it's Unbound > AdGuard. And everything works like it's suppose to, since Unbound can start resolving, no startup issues are happening after a reboot which is great.

Only thing that sucks is on AdGuard the queries only show 127.0.0.1, ::1, and the Fe80 IPv6 addresses. Instead of the actual client name (hostname). Is there a way around this? Some setting within OPNsense?


Presumably it is simply because AdGuard is upstream from unbound in their setup, and therefore all DNS requests received by AdGuard come from unbound (ie localhost)

Indeed, I'm using Unbound for local and portforward LAN directly to AdGuard

Quote from: FormBurden on December 18, 2021, 09:01:44 PM

Only thing that sucks is on AdGuard the queries only show 127.0.0.1, ::1, and the Fe80 IPv6 addresses. Instead of the actual client name (hostname). Is there a way around this? Some setting within OPNsense?

You set the IP for Adguard DNS in your DHCP DNS settings.

I ended up fixing it. Had some wrong settings in the upstream DNS server on AdGuard that wasn't pointed to my Unbound.