Hacking [DNS-U] New Update Blocking DNS Server

  • Thread starter Thread starter Ninja_Carver
  • Start date Start date
  • Views Views 74,765
  • Replies Replies 142
  • Likes Likes 42
Good evening,

I just tested these DNS ==> Primary DNS 52.40.86.243 and Secondary DNS 127.0.0.1 and it works .Ma wii U connects to the internet but on the other hand I can not go on the Eshop.

Thanks to Ninja Carver

Awesome! Thank you for sharing this!
 
I've set my DNS to the right adresses but for some reason i can still access Eshop and the System Update.
Even the chncdcksn DNS didnt work for me for whatever reason and i can't figure out why...
 
I've set my DNS to the right adresses but for some reason i can still access Eshop and the System Update.
Even the chncdcksn DNS didnt work for me for whatever reason and i can't figure out why...

It's likely that your ISP is redirecting all DNS traffic to their own DNS servers... the only solution in this case would be to run your own proxy or DNS resolver inside your home network to reject the update servers.
 
It's likely that your ISP is redirecting all DNS traffic to their own DNS servers... the only solution in this case would be to run your own proxy or DNS resolver inside your home network to reject the update servers.

Wow that sucks hard.... :/ my router also doesnt have URL Blocking so i am totally screwed. For now i have my Power Off when not playing so the Wii U can't update while i am sleeping or so. I hope that is good enough for now....

I still don't get why Nintendo can push those updates over night while on the 3DS it's forbidden for them and it needs to ask for the update.
 
Just to throw my alternates into the ring here... I've converted the TitleDB.com secondary and tertiary into recursive DNS servers that will block updates as well... The servers I'm operating are:

ns2.titledb.com, hosted out of the Netherlands:
081.004.127.020

and ns3.titledb.com, hosted out of LA:
168.235.092.108

Set your primary to whichever is physically closest to you for optimal performance.

thanks
 
NOW IN PRODUCTION (:

With TubeHax being relatively unreliable and going down sporadically, I spun up a highly-available Anycast constellation in the Amazon AWS Cloud that can effectively, and resiliently block Nintendo updates via the common DNS method.

My server can be used in conjunction with TubeHax (as primary or secondary DNS), adding further resilience to your WiiU's internet connection, rather than taking you down entirely if one of the servers goes down.

Please apply these settings on your WiiU device, only, not on your router.

Set Primary DNS to 52.40.86.243
Set Secondary DNS to TubeHax or 127.0.0.1

wtLPc6X.png

Just to throw my alternates into the ring here... I've converted the TitleDB.com secondary and tertiary into recursive DNS servers that will block updates as well... The servers I'm operating are:

ns2.titledb.com, hosted out of the Netherlands:
081.004.127.020

and ns3.titledb.com, hosted out of LA:
168.235.092.108

Set your primary to whichever is physically closest to you for optimal performance.

A huge thank you to the both of you.
I usually don't bother posting but this is indeed an obligatory post.
Never ceases to amaze me how fast things will get updated, fixed or replaced in this and most communities.
Well done and again, thank you very much.
 
Yep, it works. Can't enter to the eShop and can use the web browsed. Everything is right in the universe. Again.
 

Site & Scene News

Popular threads in this forum