When it comes to OpenDNS and Tubehax DNS, it's unclear which one people prefer. Most people use Tubehax DNS it seems, while some users claim that it didn't work for them. One thing to know about Tubehax DNS is that it's hosted by Smealum, and can be shutdown at anytime. So openDNS may be a little more secure on staying up when you need it since you created it under your own IP.
I personally have a static IP which makes things easier. Having a Dynamic IP means that it will change and never be the same, which can be risky. I once read that tubehax DNS is best for dynamic IP, but unsure about this user's speculation. Maybe it's because OpenDNS requires the use of a PC program and your computer to be on. Be careful if you're using a dynamic IP and also using OpenDNS.
You can test if you have static or dynamic IP HERE
Both are very easy to set up, though Tubehax is the easiest. What DNS do you prefer and why?
Under a static IP, I'd say both are reliable.
There's two kinds of updates that I'm trying to better understand how they're triggered, and if it's possible to disable them.
Update type 1: Installs in the background without you knowing automatically against your will, the most feared type of update. This is new and exclusive to the Wii U, not seen on the 3DS.
Update type 2: Downloads an update popup/nag that comes up every now and then to ask you to update, which you can easily say no to so it's not so scary. In case of the 3DS, update type 2 can ONLY be triggered if you fold your 3DS into standby mode. So I wonder what can trigger this to happen on the Wii U.
This guide warns you to turn off "quick start menu" after updating to 5.3.2 or else. But why, does that stop automatic updates (update type 1) and is there any further ways to prevent automatic updates? I'd much rather block their servers AND disable automatic updates (Update type 1) to be safe. I wouldn't want the DNS to not function one day, and update type 1 will occur when I could've prevented it by disabling something.
From what we know now, users can only tell you something like "several users have had their Wii U automatic update, and I don't know how/why it happens and what to do to prevent it. And to top it off, some users claim the DNS trick didn't work out. So we need a better understanding here.
I personally have a static IP which makes things easier. Having a Dynamic IP means that it will change and never be the same, which can be risky. I once read that tubehax DNS is best for dynamic IP, but unsure about this user's speculation. Maybe it's because OpenDNS requires the use of a PC program and your computer to be on. Be careful if you're using a dynamic IP and also using OpenDNS.
You can test if you have static or dynamic IP HERE
Both are very easy to set up, though Tubehax is the easiest. What DNS do you prefer and why?
Under a static IP, I'd say both are reliable.
There's two kinds of updates that I'm trying to better understand how they're triggered, and if it's possible to disable them.
Update type 1: Installs in the background without you knowing automatically against your will, the most feared type of update. This is new and exclusive to the Wii U, not seen on the 3DS.
Update type 2: Downloads an update popup/nag that comes up every now and then to ask you to update, which you can easily say no to so it's not so scary. In case of the 3DS, update type 2 can ONLY be triggered if you fold your 3DS into standby mode. So I wonder what can trigger this to happen on the Wii U.
This guide warns you to turn off "quick start menu" after updating to 5.3.2 or else. But why, does that stop automatic updates (update type 1) and is there any further ways to prevent automatic updates? I'd much rather block their servers AND disable automatic updates (Update type 1) to be safe. I wouldn't want the DNS to not function one day, and update type 1 will occur when I could've prevented it by disabling something.
From what we know now, users can only tell you something like "several users have had their Wii U automatic update, and I don't know how/why it happens and what to do to prevent it. And to top it off, some users claim the DNS trick didn't work out. So we need a better understanding here.
Last edited by MattKimura,