I could be completely off-base, but here's a possible theory of what's happening: The DNS is the web's address book. It converts names like 'amazon.com' to an IP address that it can directly connect to. When a DNS entry for a particular address gets corrupted, the system tries to go somewhere that won't work right, if at all. Each device has an internal, cached copy of the DNS, which sometimes can get corrupted when there's repeated connection failures, as what can happen when there's an interruption in the satellite connection or from a poor wifi connection (e.g., If a device is too far away from the modem). Every time you try to use the internet the DNS gets called, and the system employs acceleration techniques to try to speed up the process, because each ping takes at least a half-second round trip due to the way satellite comms works. It's very possible that when you hit FAP, your system is getting overloaded from repeated DNS failures - why you're seeing a problem with the system's ability to 'see' the DNS Accelerator (which may be a DNS entry in itself). This could be for any bunch of reasons, but I'm mostly thinking be the use of secure sites (as in https:\\, which is virtually everything) and/or the use of secure Virtual Private Networks (VPNs, which some phones and tablets now employ by default and should be disabled). Without going into too much detail, those kinds of things take a lot longer to return a result on standard satellite, which may be viewed as a 'failure' by one or more of your devices whenever it gets used. If a device thinks there's a failure, it may try again and again, ultimately crushing the DNS entry, which is going to fail by default. When things finally settle down, the DNS Accelerator re-finds itself and the error disappears... until you use it again and the cycle repeats. Again, just a theory, but I would look at your devices' settings to see if there is something like a VPN being used somewhere.
... View more