SSH and adguard not reachable

[EricPerl]

The second set of instructions (from the forums) is decent and concise.
It's only missing the primary DNS tick (that checkbox might be more recent than the post).
As mentioned earlier, 53530 instead of 5353 might avoid a conflict down the line.

If you have a NAT PF rule to force clients through YOUR DNS server, disable it for now.
Get the client -> AGH -> Unbound -> local or upstream chain going first.
Then lock it down.

If you suspect FW rules, check the FW live view (enable logging of default rules).
Use tools to verify the setup (nslookup, dig, ...).

Then maybe you can optimize (for example only use unbound for local, using the example in the AGH DNS settings).

[guliver235]

Finally, almost working I had uninstalled the plugin and reinstalled it again I left it to port53 I disabled unbound AdGuard was working with the generic settings and getting queries After that I enabled unbound with port 53530, and in AdGuard DNS settings I replaced the generic one with 192.168.50.1:53530 except in the Bootstrap DNS servers.
I said almost working since one of my 2 VLAN does not get internet, but It might come from my firewall, I am going to get concentrate on very soon.
 So the problem was 30% the AdGuard got an issue until I DL a new one and the other 70% was about myself and my lack of understanding the way to do it, actually I learned a lot because of you guys,
so again, thanks a bunch.