Using AdguardHome and Control D on OPNsense - help needed

[burntoc]

My current setup is ADGH is running on 53 with its upstream pointing to Unbound on an alternate port.  For Unbound, I have DOT set up to use NextDNS and it works well.

I want to test with Control D in this role vs NextDNS.  I thought using the DOT hostname they provided, port 853, and an IP address of something like 76.76.2.11 would set it up - and it seemed okay.  Enabled this, disabled the NextDNS entries, and DNS continues to work for the most part.

Thing is, even after creating a device and playing with different Control D settings I can't see any traffic or other analytics reflected.  Running an online DNS check, it does appear Control D's servers are being used though.  I did also run into a Zoom call being blocked this morning and when I disabled the Control D entry and re-enabled the NextDNS items I was good to go.

I know there is a CLI command that will run an automated install, but I'm worried it assumes Control D will be the primary resolver or that it may do other undesired things.  Does anyone have a setup working and if so, would you share the secrets to success?

[yegor]

Heya, I'm from Control D. Your assumption is partially correct, but there are ways to avoid it. See this guide I wrote: https://github.com/Control-D-Inc/ctrld/wiki/pfSense-and-OPNsense-Operations-Guide