Adguard Home + unbound in ubuntu 22.04

[lukasig]

Hi
noob here...

I've been trying to set up adguard home with no success. This is the setup:

• running adguard in a docker container on a Ubuntu 22.04 server (I have tried installing in ubuntu directly but I get the exact same behaviour).
• I also have unbound installed AND a reverse proxy running (caddy)
• ports 80 and 443 are used by caddy for external nextcloud AIO access
• router is set up to use the local address of the ubuntu server for DNS (192.168.x.x)
• in the Upstream DNS servers box in adguard DNS settings i only put 127.0.0.1:5335

Problem:
I can access the web interface on port 3000 and everything seems to be working fine but the problem is that almost no ads are blocked. I have blocked access to 9gag.com in adguard blocked services page for faster debug.

• 9gag is blocked on the machine adguard is running on.
• On my personal laptop no ads are blocked (even after reboot).
• On my phone (android 12) ads are blocked including 9gag but youtube still runs ads.
• On an older phone (android 6) no ads are blocked and 9gag is accessible.

other info:
I installed adguard using this docker run command:
sudo docker run --name ADguard --network host --restart unless-stopped -v /opt/adguardhome/workdir:/opt/adguardhome/work -v /opt/adguardhome/confdir:/opt/adguardhome/conf -d adguard/adguardhome
/etc/resolv.conf shows:

nameserver 127.0.0.1
nameserver 192.168.x.x
search local

/etc/systemd/resolved.conf.d/adguardhome.conf shows:

[Resolve]
DNS=127.0.0.1
DNSStubListener=no

/etc/unbound/unbound.conf is a copy-paste from this tuttorial.

Can anyone point me in the right direction?
Thanks

[lukasig]

I managed to (hopefully) narrow down where the problem might be.
Only devices that are using ipv4 AND ipv6 on their DNS settings bypass adguard. So I'm guessing that something is not quite right with ipv6 in my setup even though i have "do-ip6: no" in my unbound.conf.
There is no option for ipv6 DNS in my router. Could that be causing the issue?

[lukasig]

Ok...
so I have finally managed to figure out what was causing the issue. It was my ISP router, which lets me configure the DNS server only for ipv4, but has no option for ipv6. At least it had an option for disabling ipv6 completely:
https://imgur.com/a/G8IhKzR
I've done that and everything seems to be ok now.