Unsure
Unsure
Unable to resolve DNS server
Nintendo Switch fails to connect to Ubiquity WiFi AP using DNS 1.1.1.1
Switched DNS to Google and issue was resolved.
You will need find, and share the domain names, that you’re having issues with.
Without them, no one will be able to do anything to assist you.
It looks like it is: ctest.cdn.nintendo.net
Where are you seeing these problems?
What country (and preferably state/region)?
What “Cloudflare Data Center” do you see?
… from the 1.1.1.1/help page, mentioned above?
Checking from multiple locations across the world, I do not see any issues resolving “ctest.cdn.nintendo.net”, through the 1.1.1.1 resolver.
Sorry, AS number is AS6167 Verizon Business
I also did a packet capture and am getting an ICMP Destination Unreachable (port unreachable) returned.
So does Cloudflare have no intention of looking into a resolution for this issue?
It seems like my previous attempt to respond didn’t go through.
I tried from AS6167, and on that network, there seem to be no issues resolving “ctest.cdn.nintendo.net”, which is pointing further to the Akamai CDN.
How exactly are you troubleshooting, from your side, when you end up with this error?
Pinging the IP addresses (e.g.ICMP traffic) works just fine, for these returned Akamai CDN IP addresses, too.
Maybe this packet capture may be able to provide some further context to the issue, assuming you’re going to share it.
The information you have provided so far, doesn’t lead to any results that are showing that there are any issues at all, with Cloudflare.
So how exactly can anyone reproduce the problem, … over and over?
I have no issues getting a DNS response from other providers. Cloudflare is the exception. I perform a packet capture upon network join of the Nintendo switch, my LAN will assign the local IP but DNS cannot complete the request. I can give a SS of the packet capture tonight or tomorrow but not sure how that’s going to help.
Can you run “ping 1.1.1.1” and “traceroute 1.1.1.1” (tracert on Windows), on a device that is connected to the same WiFi AP, and share the results?
And “ping 1.0.0.1” and “traceroute 1.0.0.1” too?
Quite interesting traceroute for “1.1.1.1”.
Can you try running one for “1.1.1.2”, and then follow up with another one for “1.1.1.1” right after that, and share the results?
Sorry just to simplify… since you have a terminal open. Does dig ctest.cdn.nintendo.net @1.1.1.1 work on your machine? If it does then the issue isn’t Cloudflare.
Thank you for the cooperation!
It seems like “10.184.93.148”, which likely is your Internet connection’s first device, and perhaps supplied to you by Comcast, is intercepting queries to “1.1.1.1”.
It has previously been mentioned in this blog post, that “1.1.1.1” had issues, because some CPE vendors were squatting on random IP addresses.
Comcast was mentioned (and thanked) near the bottom of that blog post, which I believe would be because they had been assisting with cleaning up the issues, that were caused by the devices, that they had been supplying their customers with.
It does however (unfortunately) look like there may still be a few broken Comcast devices here and there.
I will therefore suggest you to contact Comcast, in order for them to assist with upgrading the firmware of their device, or replacing the broken device, if firmware upgrades are impossible.
My provider is Verizon, not Comcast.
