- Joined
- Aug 7, 2008
- Messages
- 2,538
- Solutions
- 1
- Reaction score
- 1,520
- Trophies
- 2
- Location
- Melbourne
- Website
- vaguerant.tumblr.com
- XP
- 4,165
- Country

This thread is really frigging long for having no answers.
The DNS which @nallar provided in this thread blocks the Nintendo update/eShop servers as well as the browser update check server. I'm not sure how much traffic nallar is prepared to deal with, so you'd have to ask him how long he plans to continue offering it.
Incidentally, I'm not convinced blocking the browser update check results in a working browser as has been widely reported here on GBATemp including nallar's above linked thread, so using this DNS will probably leave you with a non-working browser if you're on or above 9.9 in addition to blocking updates/eShop, but tradeoffs, I guess. You could always set up your own with OpenDNS, or if you're on 9.8 or below then blocking the update check will have zero effect (positive or negative) anyway.
Many claim blocking the check after having used the browser at least once to cache the update check's successful result will leave the browser to operate indefinitely. I think it's more likely that this will only result in a browser that works until the next time it attempts an update check, at which point it is blocked, fails, and tells the user the browser can't be used in this network environment. Feel free to disprove my speculation, though.
The DNS which @nallar provided in this thread blocks the Nintendo update/eShop servers as well as the browser update check server. I'm not sure how much traffic nallar is prepared to deal with, so you'd have to ask him how long he plans to continue offering it.
Incidentally, I'm not convinced blocking the browser update check results in a working browser as has been widely reported here on GBATemp including nallar's above linked thread, so using this DNS will probably leave you with a non-working browser if you're on or above 9.9 in addition to blocking updates/eShop, but tradeoffs, I guess. You could always set up your own with OpenDNS, or if you're on 9.8 or below then blocking the update check will have zero effect (positive or negative) anyway.
Many claim blocking the check after having used the browser at least once to cache the update check's successful result will leave the browser to operate indefinitely. I think it's more likely that this will only result in a browser that works until the next time it attempts an update check, at which point it is blocked, fails, and tells the user the browser can't be used in this network environment. Feel free to disprove my speculation, though.





