Diversion works for me and I recommend it to other people.
Lately I saw a few ads sneaking in and tried to debug what happens. I don't have IPv6 enabled on the router or the ISP, but I suspect this is related to AAAA queries over IPv4.
Disclaimer: I know I don't know enough about the difference between nslookup, dig and resolvectl query, which may be confusing some of my observations.
The server I am trying to block is ads.bridgebase.com
1. An A query returns the pixelsrv-tls IP as expected
2. An AAAA query returns the authoritative answer which contains a couple of CNAME records and a valid IPv4 address
3. Sometimes the real address, the one that is within the AAAA query is used and I am trying to prevent this.
Clearly, the blocking of the A query works as designed. The only way the real IP address sneaks in is because of the AAAA queries. They are supposed to be for IPv6, which I am not using, but clearly something is not right. I searched and it looks like stopping the AAAA queries is lost cause.
I found Diversion blocks the AAAA queries automatically and sucessfully when IPv6 is enabled on the router. I tried that, it works, no issues. It also seems to solve my issue. There is no harm that I can see since my ISP does not support IPv6 yet, but I plan to change ISPs and the new one supports IPv6. That is why I don't want to enable IPv6 on the router.
Is there a way to make Diversion to block the AAAA queries even when IPv6 is not enabled on the router? I understand it is an optimization, keeps the blocklist/memory usage smaller, works faster, etc, but can we have it as an option, please?
Thank you!
Lately I saw a few ads sneaking in and tried to debug what happens. I don't have IPv6 enabled on the router or the ISP, but I suspect this is related to AAAA queries over IPv4.
Disclaimer: I know I don't know enough about the difference between nslookup, dig and resolvectl query, which may be confusing some of my observations.
The server I am trying to block is ads.bridgebase.com
1. An A query returns the pixelsrv-tls IP as expected
2. An AAAA query returns the authoritative answer which contains a couple of CNAME records and a valid IPv4 address
3. Sometimes the real address, the one that is within the AAAA query is used and I am trying to prevent this.
Clearly, the blocking of the A query works as designed. The only way the real IP address sneaks in is because of the AAAA queries. They are supposed to be for IPv6, which I am not using, but clearly something is not right. I searched and it looks like stopping the AAAA queries is lost cause.
I found Diversion blocks the AAAA queries automatically and sucessfully when IPv6 is enabled on the router. I tried that, it works, no issues. It also seems to solve my issue. There is no harm that I can see since my ISP does not support IPv6 yet, but I plan to change ISPs and the new one supports IPv6. That is why I don't want to enable IPv6 on the router.
Is there a way to make Diversion to block the AAAA queries even when IPv6 is not enabled on the router? I understand it is an optimization, keeps the blocklist/memory usage smaller, works faster, etc, but can we have it as an option, please?
Thank you!