Quote:
Originally Posted by SteveEisenberg
Warning: Techie Post Ahead - And, Worse Than That, Poster May Not Know What He's Talking About
I shouldn't get impatient just when the down time is about to end -- but when it is a DNS problem, shouldn't we get able to use the site by typing an IP address?
Currently, on OpenSUSE Linux, I can get to www.readingthenet.com, using the web site name, with the Konqueror or Firefox browser. Same from Chrome on Windows 8. And, pinging www.readingthent.com, I get an IP address of 216.239.38.21 from Linux and 216.239.32.21 from Windows. But either of those IP addresses gives a 404 error from Google.
Doesn't this mean that there must be a working IP address for www.readingthenet.com, the problem being that the DNS server the Kindle is using returns the wrong one -- probably one of the ones returned by ping? Is there some way to bypass the Kindle DNS server by putting in the same IP address my PC DNS server is returning? And is there some way to find out the IP address a PC browser is actually using?
This brings up the question of what DNS server I am using on my PC. On the Windows side, it is definitely Google Public DNS. On the Linux side, I haven't bothered switching from the default DNS, so I guess it is still Verizon. That's the only way I can account for getting different PING results on Windows and Linux.
This is quite consistent with Robin's description of the "DNS hosting" being "messed up"  |
That is because the entry in the DNS server is messed up. It returns an address that suggest a 6in4 ip address, but there is no ipv6 address. Then it would not work to enter the ip in the browser. Look at output from nslookup and dig (my dns server xxx ed out, see spoiler). This does not add up: there is no ipv6 entry, even though the ip addresses suggest ipv6 in some kind. Broken DNS record, wrongly setup DNS server. Broken. As for multiple ip addresses, that is to balance load - not everybody will go to same server.