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
I see a lot are concerned about their IP's changing so I'm going to take a different approach here.
Although one of the concerns about being a public recursive DNS server is being used in a DNS amplification attack, I'm going to open this up and see what happens and see what kind of charges I accrue (lol). Maybe at that point I'll ask for donations :D

Set Primary DNS to 52.40.86.243
Set Secondary to 127.0.0.1

Can't connect with this
 
Can't connect with this
From the first post, the new IP is 35.164.240.189.

You can also use one of my DNS servers as your secondary, so your system will still keep working during future maintenance:

Los Angeles, USA: 168.235.092.108
Alblasserdam, NL: 081.004.127.020


Use the one nearest to you, as the delay due to distance does actually become noticeable if you're going half way around the world.
 
OMG thank you sooooooooo much man the dns i was using no longer wanted to work i think i had tubehax
it just randomly stopped wanting to boot the homebrew launcher
i'm going to get a ds game so i can haxchii sounds the best way so far :)
but this works as well for me and thanks now i can use my loadiine files
or use my cfw.img to bypass the dlc and virtual console check
 
I couldn't figure out what was causing error code 106-0112 in Mario Maker course world after updating to version 1.45. I finally figured out that TubeHax DNS was down and switched over to your server. Everything is working great again. Thanks!
 
Well just got a question. when I input the 35.164.240.189, the wii u automatically add an zero or prefix this DNS IP with zero. For instance, 35.164.240.189 to 035.164.240.189, and 127.0.0.1 to 127.000.000.001. Just wonder if that is normal and will block the wii u update?
 
Well just got a question. when I input the 35.164.240.189, the wii u automatically add an zero or prefix this DNS IP with zero. For instance, 35.164.240.189 to 035.164.240.189, and 127.0.0.1 to 127.000.000.001. Just wonder if that is normal and will block the wii u update?
That's normal
 
Where do these DNS names come from? TubeHax makes sense, but Dualhax, dns-u, etc?

I'm to personally refer to this as NinjaDNS,

Sure, no one will know what I'm talking about when I ask questions, but it makes more sense to me.
 
Where do these DNS names come from? TubeHax makes sense, but Dualhax, dns-u, etc?

I'm to personally refer to this as NinjaDNS,

Sure, no one will know what I'm talking about when I ask questions, but it makes more sense to me.
How does "DNS-U" not make sense?

"Dualhax" I agree is awful considering it is neither of those
 
I've been trying to set this DNS for the past 1 hour or so, without success. It fails the connection test. Even if I ignore the connection test, it wont load any website. What I am doing wrong?
 
I've been trying to set this DNS for the past 1 hour or so, without success. It fails the connection test. Even if I ignore the connection test, it wont load any website. What I am doing wrong?
IIRC the failed connection test is normal but you should be able to access most of the internet unless you entered the wrong IP or you're connecting your WiiU through something that cannot provide internet access to your WiiU (ex: a buggy/turn-off bridge or router).

From what I can tell, this DNS is working atm.
If you don't have dig or drill installed on your computer you can use that page to check (server = address, either IP or url, of DNS; domain = a domain to be resolved to an IP address; if you don't get an ANSWER section, domain can't be resolved with server set, else you'll see IP(s) that this domain is resolved to).
 
I've been trying to set this DNS for the past 1 hour or so, without success. It fails the connection test. Even if I ignore the connection test, it wont load any website. What I am doing wrong?

The system is up and running.. there is an easy way to verify from your computers.

from a command prompt/terminal/shell type the following command:

> nslookup cbvc.nintendo.net 35.164.240.189

If you get a response like this (that results in 127.0.0.1), you know its working on my end...

Code:
C:\Users\carver>nslookup cbvc.nintendo.net 35.164.240.189
Server:  ec2-35-164-240-189.us-west-2.compute.amazonaws.com
Address:  35.164.240.189

Name:    cbvc.nintendo.net
Address:  127.0.0.1
 
Last edited by Ninja_Carver,
Code:
C:\Users\carver>nslookup cbvc.nintendo.net 35.164.240.189
Server:  ec2-35-164-240-189.us-west-2.compute.amazonaws.com
Address:  35.164.240.189

Name:    cbvc.nintendo.net
Address:  127.0.0.1

(I repeat myself, but tagaya servers should not be blocked.)
 
Last edited by BDS,
You shouldn't. Check the discussion here. Only four (or even less) domains need to be blocked.
Hi BDS - I'm always willing to take the communities input into consideration. My concern with your recommendation is that the information you're presenting is specific to NDS? I'd rather err on the side of caution unless blocking this host is actually creating problems for people. Let me know. Thanks.

--------------------- MERGED ---------------------------

I repeat myself, but tagaya servers should not be blocked.
tagaya servers unblocked as per @BDS -- REASON: negatively impacts users by preventing updates to games.
 

Site & Scene News

Popular threads in this forum