said by seagreen:
Ask your host. Even on shared hosting there's a way to access a site before DNS propagates.
Host said, "viewdns.info cannot realistically claim to speak for every DNS server in the world, while they might have a few servers that are geographically diverse they are surely also all servers that have never before had to serve the DNS for carriage-house-inn.com Therefore in every case they will have to come to us to fetch fresh DNS information which by definition must then be the latest data, so the test appears to have no value at all for a small site such as this.
What you are seeing is the string of devices on the physical route between you and the website, where one or more devices will have cached older information for a period of a day or maybe more. Satellite providers are particularly known for excessive caching to minimize their resource use
. That information is not and cannot be queried by viewdns.info." (bold and italics mine)
In any case, another check at »viewdns.info/propagation ··· -inn.com
showed (Oklahoma, USA) with a green checkmark, which had been showing as a "timeout" before. So once again, I restarted my computer, modem, and network router, deleted my browser cache and cookies, ran the command prompt to flush my DNS cache, and disabled web acceleration. After all of that, the site FINALLY came up in my browser and appears to be working fine.
said by seagreen:
If it's not just Hughesnet I may move this thread over to a different forum better suited to the question.
It may not have been JUST Hughes, but I don't think Hughes was making things any easier. Maybe I just needed to wait longer and it eventually would have come up without jumping through all those hoops. At least I can finish tweaking up the site now. Thanks everyone for all your suggestions.