Yep on both accounts.
Chrome, Firefox, and Android all can auto-enable DoH depending on version and environment. So depending on policy on running/configuring those, "catch" part (or, rather - coming up with a credible proof user did that intentionally) might be tricky.
Nonetheless - I personally would rather use a local caching dns resolver instead. There are some that could be configured to do the "answer from stale cache, then refresh in the background" thing. That should alleviate GP's frustrating experience quite well, while not giving CISO a reason to rage.
No way you would get fired for this, come on man. Maybe someone from IT would ping you to turn it off, worst case.
Depends on the workplace, but I've definitely seen people fired for less.
Re:So my ISP was hijacking my DNS
by BizarroLand on Thursday November 05, 2026 @12:15PM
(#50381663)
If you're not working on something highly secretive and valuable (with a salary to match) then they're doing you a favor by flipping out over something so stupid.
Happened to me once, my computer had Little Snitch block fortinet. Got a nice message to look into why. Suddenly started calling home.
It’s a university network so things are not as strict as other work places.
They also do not pay for my device, so it’s only fair I can configure things my own way.
I’m pretty sure the worst that could happen is they would ask me to turn it off.
But I guess that if they let you do it they're probably not competent enough to catch you.