I had that also about an hour ago. I just chalked it up to either the occasionally-flaky network setup we have at my office, or the propagation of the new DNS records. That could mean we hit it at a moment after the old information had expired on our respective DNS servers and they had a problem initially getting the new address. I believe most DNS servers these days are caching, and that could be related. But who knows.
Edit: Although I should mention (as just now I noticed again), there are several times when my browser sits for a little while at "Resolving satelliteguys.us..." before moving on. I think when the problem above ("not found") occurred it more likely could have just been that one of those pauses took too long and the browser (or DNS server) timed out returning that the name did not resolve. But that's not saying the problem is at one end or the other definitively.