There's a
90DNS Tester that you can run from your Switch to check if DNS MITM is actually working. Good to know that 90DNS has it's own script as well, thanks for mentioning that.
There's also
this fix. I haven't tested it personally since I'm using Exosphere and DNS MITM. As for 90DNS, it requires that you manually set it up for every wireless connection. There's
90DNS setter as well, but I haven't tried it out yet.
Only thing they are currently missing in their hekate_ipl.ini file is the
kip1patch=nosigchk line in both CFW configurations. Without them I believe that sigpatches won't work when chainloading fusee. (Provided I'm reading it correctly through sys-patch, which says
Patched instead of
Patched for fs patches, i.e. sys-patch did the patching instead of sigpatches.)
I've read it couple of times already but I couldn't find any info about this? Can you show me the source? Too bad if it's true, DBI really is an amazing tool.
It doesn't hurt to have exosphere's prodinfo blanking enabled while also having 90DSN/DNS MITM in place. Ever since 17.0.0 firmware got released and they fixed the prodinfo blanking, resulting in an error in both OFW and Atmosphere. Therefore, to me at least, it serves as a warning of sorts that maybe, just maybe, DNS MITM / 90DNS stopped working properly and my console tried to connect to the Nintendo servers, resulting in Atmosphere crashing with a specific error (can't remember which one right now, I'll have to look it up later).
@impeeza wrote a detailed explanation when I asked him the similar question. You can check his reply
here.