nanoDNS works on home router but cuts internet completely when using mobile hotspot (FW 9.00) #11

New issue

Open

opened 2026-09-03 22:02:00 -05:00 by olzs7 · 0 comments

olzs7 commented

2026-09-03 22:02:00 -05:00

(Migrated from github.com)

Hello, thank you for developing nanoDNS. I am experiencing a specific networking issue on PS4 Pro (FW 9.00) using the nanodns-ps4.elf payload.

When connected to my home router, setting DNS to 127.0.0.1 and running the payload works perfectly: the internet functions normally, and Sony update servers are successfully blocked.

However, when I switch my internet connection to a mobile hotspot, running the exact same setup causes the internet connection to drop completely instead of passing through the local DNS server.

It seems that mobile hotspot tethering handles local interface bindings or DNS forwarding (127.0.0.1) differently than standard home routers, causing the payload's proxy/DNS redirection to fail.

Is there a limitation or a configuration adjustment needed in nanodns.conf to support mobile tethering interfaces?

Thank you for your time and help!

Update:
I found the root cause and a working solution for this issue!

The problem happens because mobile hotspot APN protocol defaults to IPv6 or IPv4/IPv6, which conflicts with how nanoDNS handles local DNS binding and IPv4 traffic forwarding on the PS4.

To fix this:
Go to Mobile Networks -> Access Point Names (APN) on the phone.
Change the APN protocol from IPv6 (or IPv4/IPv6) to IPv4 only.

Once switched to IPv4,
the hotspot mimics a traditional router network stack, and nanodns-ps4.elf works perfectly—the internet functions normally while Sony update servers are successfully blocked. You might want to mention this compatibility behavior in the documentation for users using mobile tethering.

Hello, thank you for developing nanoDNS. I am experiencing a specific networking issue on PS4 Pro (FW 9.00) using the nanodns-ps4.elf payload. When connected to my home router, setting DNS to 127.0.0.1 and running the payload works perfectly: the internet functions normally, and Sony update servers are successfully blocked. However, when I switch my internet connection to a mobile hotspot, running the exact same setup causes the internet connection to drop completely instead of passing through the local DNS server. It seems that mobile hotspot tethering handles local interface bindings or DNS forwarding (127.0.0.1) differently than standard home routers, causing the payload's proxy/DNS redirection to fail. Is there a limitation or a configuration adjustment needed in nanodns.conf to support mobile tethering interfaces? Thank you for your time and help! Update: I found the root cause and a working solution for this issue! The problem happens because mobile hotspot APN protocol defaults to IPv6 or IPv4/IPv6, which conflicts with how nanoDNS handles local DNS binding and IPv4 traffic forwarding on the PS4. To fix this: Go to Mobile Networks -> Access Point Names (APN) on the phone. Change the **APN protocol** from IPv6 (or IPv4/IPv6) to **IPv4 only**. Once switched to IPv4, the hotspot mimics a traditional router network stack, and nanodns-ps4.elf works perfectly—the internet functions normally while Sony update servers are successfully blocked. You might want to mention this compatibility behavior in the documentation for users using mobile tethering.