DNS64 prefix not being synthesized for some IPv4-only domains #7514
Description
Prerequisites
-
I have checked the Wiki and Discussions and found no answer
-
I have searched other issues and found no duplicates
-
I want to report a bug and not ask a question or ask for help
-
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
FreeBSD, AMD64 (aka x86_64)
Installation
Other (please mention in the description)
Setup
On a router, DHCP is handled by the router
AdGuard Home version
107.55
Action
Enabled DNS64 on AdGuard Home and specified the default DNS64 prefix as follows:
use_dns64: true
dns64_prefixes:
- 64:ff9b::/96
My AdGuard Home server is running on an OPNsense router and is using quad9 DNScrypt as its upstream resolver.
Expected result
IPv4-only domains should include the synthesized DNS64 address.
Actual result
Some IPv4-only domains included the DNS64 address in the response (in this case completion.amazon.com). Others did not include the DNS64 prefix (www.reddit.com). It appears that the issue occurs when the requested domain is an alias to another name.
Additional information and/or screenshots
No response