Yesterday afternoon about one o’clock eastern time, we began a migration to a new server. You weren’t supposed to notice the change. Or, if you did, it’d be like, “Wow! Look at how much better this site performs now!” We had it planned so visitors would just connect to our old server until the DNS change propagated the Internet and — voila! — they’d suddenly be visiting us on our new and improved server, without even knowing.
It sounds like a plan, eh? That’s what we thought, until it didn’t work out.
We moved a total of seven domains to the new server and watched as one by one they began to show up online with the domain resolving to the new server. Until it was FOSS Force’s turn. Until it was time for the most important site involved in this move.
When the nameserver change hit for FOSS Force, the site simply quit resolving and browsers starting offering excuses. Of course it turned out to be a simple DNS configuration error, but it took a while to fix. We had to wait until the nameserver change propagated to our tiny little corner of rural North Carolina before we could access the situation to get a handle on what needed to be done.
Oh well, what’s done is done. We’re back. If you missed us, we’re sorry. We promise never to do that again. If you didn’t miss us, no harm no foul…
I don’t know who coded your web page. About all I can say is (A)bort, (R)etry, (F)ail
It looks AWFUL!
Never mind the new server which is still serving an almost indecipherable horribly coded web page that DOESN’T even work with Firefox – on WINDOWS! What did you use to test your web pages with? INTERNET EXPLORER?!
IDIOTS.
@Annoyed The site looks fine from here. Is it broken on your end? If you could please share some information, we’re still working to get the new server configured. Any information you give us will be appreciated.