4GEE Wifi Not working with Kindles

[AndyJBuchanan]

Hello! I've been trying to connect my Kindles ( A Paperwhite from a couple of years ago, and an older 7" model ) to the 4GEE and it's connecting okay but telling me the WiFi is not connected to the Internet. 

I have checked on another device, and it is connected to the Internet fine. I can browse and upload and download from everywhere just fine.

Is there a configuration step needed on the 4GEE for Kindles?

[mikeliuk]

Unfortunately I don't recall where they are typed in. I tried just typing into a search but got nothing back. I don't really think they are useful here. I only looked them up to try to check an IP address was assigned. Best to ignore unless debugging 3G mobile access if the paperwhite variant has that.

The DNS change is probably the best hope and 8.8.8.8 is probably the simplest one that everyone will remember and try if it is to be done on the device itself. After that I think it would be asking Amazon what the criteria is that the paperwhite determines it has internet access. It's possible the problem may entirely disappear of its own accord and it decides it is online tomorrow with essentially nothing changed to fix.

If the Paperwhite always presents that error on multiple different wifi access points (e.g. mobile hotspot and neighbour's internet), it's possible the device itself has a fault (e.g. I had a Paperwhite unable to make a 3G connection when it should and collected sufficient evidence that Amazon replaced it with the first gen Oasis).

Right, I've found some codes that actually work. They begin with ";" which jogs my memory. Only the wifi and the wan ones might be of use. Be careful not to brick a Kindle. Sadly there's no wifi/internet test code at this link. https://ebooks.stackexchange.com/questions/152/what-commands-can-be-given-in-the-kindles-search-box

[XRaySpeX]

On the Kindle 3 you could obtain diagnostics thus:

You can send us the logs by doing the following:

1. Open the Search box by selecting that option from the Home screen menu.
2. Type ";dma" (without quotation marks) into the search field. You can find the semi colon by pressing the SYM key.
3. Hit "Search My Items". Note there is no feedback, but new files are stored.
4. Connect your Kindle to your computer using the USB cable and open the “Documents” folder on your Kindle.
5. Copy the two .TXT files from the Kindle Documents folder; these files start with:
   All_logs_as_of
   Wpa_supplicant
6. These files may contain something useful for this matter. (Attach the log files to an e-mail and send the e-mail to: kindle-support@amazon.co.uk.)

[AndyJBuchanan]

Hey thanks for this info. On my Kindle the code was ;dm and that wrote out the device logs.

There's about 100MB of them so it might take me a while to cull through them looking for errors! 

FWIW ;711 shows the current configuration. Not helpful for current problem but could be handy to know in future. 

[AndyJBuchanan]

Well, that was some serious spelunking.

210806:203626 wifid[1791]: E netu:core_dns_request:host=dogvgb9ujhybx.cloudfront.net, herr=Host name lookup failure:res_nquery failed

^^ This is where it all goes sideways. Not really sure what to do with the info though. My main broadband resolves that no problem (143.204.170.158). 

Why would EE DNS not resolve that?

[XRaySpeX]

What resolves to 143.204.170.158 ?

[AndyJBuchanan]

dogvgb9ujhybx.cloudfront.net

(as in the error message)

[XRaySpeX]

Didn't here but seems to keep changing:

1. nslookup dogvgb9ujhybx.cloudfront.net
   Server: BrightBox.ee
   Address: 192.168.1.1

   Non-authoritative answer:
   Name: dogvgb9ujhybx.cloudfront.net
   Addresses: 54.240.168.25
   54.240.168.36
   54.240.168.77
   54.240.168.10

2. nslookup dogvgb9ujhybx.cloudfront.net
   Server: BrightBox.ee
   Address: 192.168.1.1

   Non-authoritative answer:
   Name: dogvgb9ujhybx.cloudfront.net
   Addresses: 143.204.194.3
   143.204.194.97
   143.204.194.165
   143.204.194.192

[AndyJBuchanan]

Well I think Cloudfront are a CDN, so they probably resolve to different addresses according to load. 

Question is, why is the 4GEE DNS servers not resolve it.

[AndyJBuchanan]

This is baffling.

The Kindle is clearly failing at this lookup, but my MBP can look it up on the 4GEE, so probably not the DNS server.

[mikeliuk]

Hi @AndyJBuchanan ,

This is a lot more debugging than I expected to see post going out to watch Black Widow!

You'll want to do a direct nslookup of dogvgb9ujhybx.cloudfront.net against your router (DNS services being provided on port 53, specify the internal LAN IP address to do the lookup against) if you feel that is the target the Paperwhite uses to determine whether or not it has internet access. If you use your phone to lookup that name, under Android 10 you would need to ensure "private DNS mode" is turned off and your 4GEE router is definitely being used to resolve names.

A search suggests there are a few other names that should be checked in the logs to see if they appear as failed lookups.

cde-g7g.amazon.com pins.amazon.com

https://www.reddit.com/r/kindle/comments/fny7m8/amazon_blocked_kindle_in_iran/

Another website gives domains and IPs that Kindles require to function so maybe there is a hiccup that one of these is not accessible, resolvable, or routable.

a4k.amazon.com
kindle-time.amazon.com

[plus quite a few IP addresses]

https://www.netify.ai/resources/applications/amazon-kindle

I can't currently determine what EE's DNS servers should be for 4GEE devices (otherwise I would test lookups and post results).

The below is slightly curious.

[x@x ~]$ for i in 8.8.8.8 1.1.1.1 9.9.9.9; do echo $i; nslookup dogvgb9ujhybx.cloudfront.net $i; done
8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: dogvgb9ujhybx.cloudfront.net
Address: 99.86.105.169
Name: dogvgb9ujhybx.cloudfront.net
Address: 99.86.105.82
Name: dogvgb9ujhybx.cloudfront.net
Address: 99.86.105.135
Name: dogvgb9ujhybx.cloudfront.net
Address: 99.86.105.141

1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53

Non-authoritative answer:
Name: dogvgb9ujhybx.cloudfront.net
Address: 65.9.84.122
Name: dogvgb9ujhybx.cloudfront.net
Address: 65.9.84.210
Name: dogvgb9ujhybx.cloudfront.net
Address: 65.9.84.15
Name: dogvgb9ujhybx.cloudfront.net
Address: 65.9.84.140

9.9.9.9
;; connection timed out; no servers could be reached

[x@x ~]$ ping -c 1 9.9.9.9
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
From 10.247.89.65 icmp_seq=1 Destination Host Unreachable

--- 9.9.9.9 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms