Glad you solved it,branded routers, the worst.Sorry, took me a moment.
Just tested on my girlfriends Laptop. Same problem there. On both PC's port 53 is only used by LocalDNS.
If I set DNS to automatic, I get Internet on the Wii U, so I believe the WiFi Adapter is okay...
EDIT: I solved it. I unplugged my router for about ten minutes and it worked again. This latest Vodafone-Routers aka easybox are complete garbage.
Sorry for wasting your time, mate.
Once again, thank you for your great app and support. Really appreciate that. Especially because no other solution works for me. DNS-U and others are completely ignored. Maybe just another stupid issue with my router...
Seriously? Didn't know that. Great...Also, Vodafone forces its Dns you can't do anything about it
I never had this issue, try downloading the latest version and rules from github, check you firewall's settings and make sure you have net framework 3.5 installed.I seem to be having problems with this LocalDNS.
Now whenever we go in to the web browser on the WiiU, the LocalDNS window that is open on my Windows file server, just quits out and disappears.
Not sure how long its not been working for as my daughter who uses the WiiU isn't sure how long she has had no Internet access on the games console. Its still version 5.5.1E however.
Its been previously working for ages with no problems, so not sure what's happening now.
I never had this issue, try downloading the latest version and rules from github, check you firewall's settings and make sure you have net framework 3.5 installed.
Then while localdns is running, open a cmd window and type nslookup google.com 192.168...(you local ip) this should query localdns and you should see the requests in its window, if it doesn't work there is something messed up with your pc's settings
Make sure it's allowed in the firewall then try manually installing .net 3.5 (in windows 10 there is some hidden setting that installs it, search on google how to), you can also try the oldest release of local dns from github since it requires 4.7Hi exelix11
I already tried downloading the newer version and the newer rules from Github but the same thing happens.
I can't see .NET Framework 3.5 listed in Programs. But there is one called Microsoft .NET Framework 4.7.1 which looks to have been installed about a week ago according to the date modified column.
When I do the nslookup command the LocalDNS window quits out again and I get no replies:
C:\Users\Administrator>nslookup google.com 192.168.1.100
Server: UnKnown
Address: 192.168.1.100
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** UnKnown can't find google.com: No response from server
If I look at the Windows Firewall inbound rules there are four entries present for the program "LocalDNS"
Thanks
deleting the update folder is probably the best method, but not everyone wants to mess with their wii u's os.IMO the 'delete update folder' method is better since then the eShop isn't blocked, but this is still pretty cool and useful.
Make sure it's allowed in the firewall then try manually installing .net 3.5 (in windows 10 there is some hidden setting that installs it, search on google how to), you can also try the oldest release of local dns from github since it requires 4.7
deleting the update folder is probably the best method, but not everyone wants to mess with their wii u's os.
And not everyone is able to do it, a friend of mine is so incompetent that failed multiple times to do it so he just gave up.
Still, this tool isn't meant to just block updates, i use it to block websites on my brother's devices as well
Good for you, I didn't think about IPv6 but ofc that doesn't work, the ip parsing code was meant for IPv4.I've just turned off IPV6 on the Network Connection of the server and now when I do the nslookup command the LocalDNS windows does NOT vanish and it resolves the Google IP address OK.
I changed routers recently and looks like the Windows server created a new network connection called "Network 3".
Perhaps I previously had IPV6 turned off and this new connection to the new router turned it back on ?
I've changed the Wii-U's DNS IP's back to that of my local server. And now when opening the web browser on the Wii-U the LocalDNS window on the server does not vanish and it stays open now doing its thing as it should.
Good for you, I didn't think about IPv6 but ofc that doesn't work, the ip parsing code was meant for IPv4.
If i get some free time this weekend i'll try to implement it or at least hande crashes.