fix(dns64): CNAME/DNAME should not be treated as hasAnswer

[L2jLiga]

Fixes #438

It seems that CNAME / DNAME themself should not be affect "hasAnswer" flag because it doesn't actually mean that domain has correct AAAA record which clients can use.

Correct me if I'm wrong, please

[Sammy1Am]

Hello there!
I've also just come upon this issue. Are you still using your own build with this fix, @L2jLiga ?
If it's working, is there anything I can do to help get this tested/merged?

[L2jLiga]

Hi @Sammy1Am,

Are you still using your own build with this fix, @L2jLiga ?

No, I've used it for a while, but now switched to another solution in front of Adguard Home to add DNS64 records. This solution just easier for me to maintain because I don't have to rebuild Adguard with this patch if I want to update to newer version

If it's working, is there anything I can do to help get this tested/merged?

It should still work, but idk what kind of help needed to get this merged, it would be nice for me to get it merged since it can simplify my setup, but I'm totally fine with what I have

[Sammy1Am]

Thanks for letting me know. Yeah, hopefully someone from Adguard might have suggestions on how to get it merged (it seems like a pretty straightforward change).

another solution in front of Adguard Home to add DNS64 records

Don't want to get too off-topic here, but do you mind sharing what you're using? Mostly I'm trying to simplify the network setup here, so I'm hesitant to add another layer, but it might still be better to do that and AGH than switch to a less convenient DNS server.

[L2jLiga]

@Sammy1Am quite simple setup:

1. Router DNS -> Unbound
2. Unbound + DNS64 -> AdGuardHome
3. AdGuardHome -> global DNS

https://github.com/NLnetLabs/unbound/blob/master/doc/README.DNS64