What is DNS behavior on mobile devices connected to an untrusted network, and what attack is possible when DNS responses are not validated?

• A.Mobile devices validate each DNS response against a certificate held on the SIM, a check the baseband performs before the answer reaches the network stack; a rogue resolver is rejected at that point, leaving spoofing impractical on a handset with an operator-issued card.
• B.Both platforms send their queries to 8.8.8.8 whatever the network offers, ignoring the DHCP-supplied resolver entirely; the attack surface is Google's infrastructure rather than the local router, leaving an untrusted hotspot unable to influence resolution.
• C.Mobile apps connect to IP addresses compiled into the binary, skipping resolution altogether; DNS matters for the browser alone, leaving app traffic unaffected by a rogue resolver.
• D.By default, mobile devices use the DNS server provided by DHCP on each connected network; without DNSSEC validation or DNS-over-HTTPS/TLS, a rogue DNS server or DNS spoofing attack can redirect app traffic to attacker-controlled IP addresses, bypassing hostname-based security controls.