I did use Brave exclusively for a while, until I realized that on mobile, Brave blatantly ignores my provided DNS (pihole). And if there is something I really don't like it's software/hardware which ignores network-wide settings (also looking at you chromecast music...)
So, I switched to Firefox on Mobile and by now I moved my desktop as well, so I have all the same addons etc. on all devices.
I've not noticed this with Brave, but wasn't it FF, out of the mainstream browsers, that pioneered DoH (ignoring local DNS). pihole I think makes the requisite setting to tell FF not to use DoH but users can override it IIRC (not the behaviour I want).
That also enables a hostile network to downgrade from DoH.
Anyway, we're investigating what might have gone wrong. So far we can't find a difference between Chrome and Brave regarding DNS and DoH configuration and configurability. More info welcome, thanks.
Not allowing the user to override it locally would be quite user-hostile! Of all the missteps Mozilla has made with Firefox (in my opinion), giving the user more control isn't one of them.
The network owner is free to allow or deny connections to IP addresses or ports and drop whatever packets they like by configuring their systems, the routers!
They do not get to determine the configuration of _my_ system.
So, I switched to Firefox on Mobile and by now I moved my desktop as well, so I have all the same addons etc. on all devices.