I had an interesting exercise with the question from subscriber Keith. First, Keith wrote me from an address that was not the address he used to subscribe to my newsletter. Generally, that’s a good way to get your question ignored.
But, he started off with a reference to the weekly email newsletter, so I thought a little more about his question — and tried to figure out which subscribed email address might be his.
Then, he used an email address in the ".asia" high-level domain, which I didn’t realize existed yet. So, I decided to follow that trail first.
The interesting part is that I transposed the letters in his domain — let’a call it example.asia, but I wrote it as eaxmple.asia. No luck with a whois command, no luck with searching for a web site. I tried to ping it.
Ping is a useful tool for debugging network connections. You can ping an IP address or ping a domain name. If you can successfully ping to the domain name, good.
If you can’t, but you can ping to the IP address, you know that either the domain name is not good, the computer is down, or the domain name servers have problems.
If you can ping anywhere else by name, you know that your domain name servers (your ISP’s, actually) are working and that the problem is at the remote server’s end of the connection.
Ping couldn’t connect to the remote computer. Then, I noticed that the IP address was somewhat familiar. Not mine, by I had seen it before.
I did a Whois on the IP address, and found that it belonged to Cox.net, my Internet Service Provider, but that this location was in another state.
I did a Google search for the IP address and found a link to an article that I had written some time ago about home networking problems that occurred because Cox.net was redirecting any unknown domain name to this strange IP address. That article about the problems caused by Cox redirecting any unknown domain name to 188.8.131.52 is Strange Home Networking Problem Solved.
I tried a Whois on .asia, and found the controlling registrar for the .asia domain. I checked there for the mis-spelled domain name, and of course, had no luck.
Somewhere is reviewing that problem, I finally realized that I was transposing (swapping) two letters in the domain name. When I spelled it correctly, it worked just fine.
So, I looked again at the question from Keith. Note that I still won’t mail the response to Keith, since his email address is not subscribed to my newsletter.
First thanks as always for your helpful, insightful weekly mails. I hope that you can be as helpful with this:
I recently purchased a Galaxy Tab 10.1 and have discovered that the Android system on it does not support Flash. I can’t even listen to BBC World Service, never mind not being able to play one of the games I enjoy. I am sure that I will find more that I cannot do. Is there an alternative out there, or are Adobe likely to come up with a solution in the near future? I think the Tab is great, but have encountered a few minor problems (with email) but the main thing (For Now) is the above — can you assist?
Unfortunately, my answer to Keith is that I don’t know and can’t help. The last I had heard, Android (at least some earlier versions) had a version of Adobe Flash.
If it’s been dropped from Android, it’s probably because (1) Flash support was in the Android operating system and (2) smartphones and tablets don’t always provide for updating of their operating systems. That leaves the tablet and smartphone user unable to get bug and security fixes for known problems — not a good thing.