In the list of objects in the Developer Tools console, select an object with a domain that should be blocked (videos-fms.jwpsrv.com).
Right click the object and choose “Block request domain”.
The expected result is that Brave does not load the page elements that are sourced from the blocked domain. This appears to function correctly when the Remote Address is blank (which appears to be when it’s an IPv4 resolved address). When an IPv6 address appears in the Remote Address, the block does not appear to work and the element is loaded and displayed.
Brave Version( check About Brave):
Version 1.17.75 Chromium: 87.0.4280.88 (Official Build) (64-bit)
No, but I’m curious why that would matter. DNS resolution doesn’t use the protocol (http v https). And the resources are explicitly being obtained from the host in the DOMAIN column. Adding www would only reference the wrong URL.
Am I misunderstanding how the functionality works?
I’m also curious about whether (or when) Brave doesn’t actually use my network configured domain name server. I have pihole configured and never even see the request pass through pihole. This also could be related to pihole not displaying DNS requests over IPv6 in its query log UI, but I didn’t check that yet.
Well, in my case of creating web pages, my DNS necessarily goes through Https to reach the DNS server through Cloudflare, in this case the company may force the DNS to go through some other IP that you are not blocking and that is why it shows you the ads or video, A second address to a subdomain example something.domain.com since I can configure a subdomain to another DNS or IP address without any problem, in the .js files of that domain you can hide second or third domains It does not detect brave browser since the rule is not installed in the blocking command.