Thank you 'ebrandsberg'.
Ok, so I've had UMA for the past three years or so (since the 8320 came out), and I've been having problems where UMA wouldn't connect. In wi-fi diagnostics, I would see that I had an IP address via DHCP, but in the UMA section, it would show an ISP or DNS error, and would show for the "serving UNC address" either n40.w79.t-mobileuncs.com or "punc.t-mobileuncs.com". I did some research and testing and found that when I was getting this error, I wasn't able to resolve this name through any of several upstream nameservers, including my ISP's (comcast), Google's recursive nameservers, 4.2.2.(1-4), etc. They all reported server fail. When I tried using OpenDNS's nameservers of 208.67.222.222 & 208.67.220.220, I was able to resolve the n40.w79 name again. Yay!
A little research found that ultradns is handling the domain "t-mobileuncs.com", but "punc.t-mobileuncs.com" appears to not resolve properly even if you point directly at the ultradns servers, despite it being the default name that will be used if the initial name pushed fails to resolve. Now, the name "n40.w79" has something to do with a parameter that is apparently pushed by t-mobile, and related to the tower you are connecting to and the supporting equipment, so it shows as a location not all that far from me if you map it out by North 40 degrees, West 79 degrees.
Anyway, it appears that for some reason, different DNS configurations make a huge difference with how reliable your UMA connections are, and with the DNS servers listed above, so far it has been solid as a rock for me. I have been having problems with this for a while, and saw others with problems on UMA, so I figured that this would be good information to post.
A little research found that ultradns is handling the domain "t-mobileuncs.com", but "punc.t-mobileuncs.com" appears to not resolve properly even if you point directly at the ultradns servers, despite it being the default name that will be used if the initial name pushed fails to resolve. Now, the name "n40.w79" has something to do with a parameter that is apparently pushed by t-mobile, and related to the tower you are connecting to and the supporting equipment, so it shows as a location not all that far from me if you map it out by North 40 degrees, West 79 degrees.
Anyway, it appears that for some reason, different DNS configurations make a huge difference with how reliable your UMA connections are, and with the DNS servers listed above, so far it has been solid as a rock for me. I have been having problems with this for a while, and saw others with problems on UMA, so I figured that this would be good information to post.
No comments:
Post a Comment