DHCP IPv6 Not Blocking

[CipherOps]

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

• [ X] I am running the latest version
• [ X] I checked the documentation and found no answer
• [ X] I checked to make sure that this issue has not already been filed

Issue Details

• Version of AdGuard Home server:
  • v0.107.2
• How did you install AdGuard Home:
  • Curl command on GitHub
• How did you setup DNS configuration:
  • AdGuard Home does DHCP
• CPU architecture:
  • i386
• Operating system and version:
  • Debian 11

Expected Behavior

I've enabled DHCP on AdGuard Home, it properly leases IPv6 addresses to clients and the clients are using AdGuard Home for IPv6 DNS requests, however they're not being blocked and not showing up in the query log

Actual Behavior

Ads are not blocked, DNS queries aren't logged.

Additional Information

IPv4 & IPv6 is assigned statically to the machine hosting AdGuard Home, DHCP is disabled on router and enabled inside AdGuard Home, clients are leased IPv6 addresses and DNS propagates correctly for IPv6 because I can compare the IPv6 on AdGuard Home to the IPv6 for DNS on devices and it matches.

[neon-dev]

Hi, as @ainar-g requested in #3203 I'm briefly stating here, that I face the same symptom but in my case it's due to the IPv6 DNS address not being sent to the clients: The one ending with 294c is the address of my cable router but I'm using AdGuard's DHCP and disabled the router's DHCP, so I have no idea how this IPv6 address can (still) be used on all my clients. The result is that some of the requests go through AdGuard and some are bypassed.

[laurentftech]

Same issue as @neon-dev here. I have created specific issue #5185. As I have set up on my Netgear router the Adguard Home ip address as DNS for IPv6, all requests seems to come from the router so I cannot set filtering rules per clients.

[cellulosa]

any info on this? I just realised my devices prioritise ipv6 most of the time, resulting in using the internet provider DNS rather than Adguard (which is hit when ipv4 is used)

[neon-dev]

@CipherOps do you have this issue in later v0.107 versions? For me IPv6 blocking and query logs have always been working after I made sure the clients were using AGH's IPv6 DNS address.