The Annoyed Man wrote:ChrisFromDallas, thanks for the answer. I lease my current server from MediaTemple, and it comes with the Parallels Plesk Panel 11.0 interface pre-installed. I've had cPanel experience, but no BlueOnyx experience; but between Plesk and cPanel, I MUCH prefer Plesk.
<snark> Media Temple is a good company. Their former customers tell me so. Let me know when you're ready to save some $$ on that Plesk box.

</snark>
I agree that Plesk is a more attractive interface. My only reservation is that Parallels seems to treat production releases like betas. The latest update will invariably break something that worked just fine before. Then they want $75 for a support incident to fix it, or you wait until the next release. Maybe that's the Russians poking their fingers at us. (Trivia tidbit: Parallels, formerly SW-Soft, formerly Plesk, is Russian. The word 'Plesk' is Russian for 'Splash'.)
cPanel is certainly not my personal favorite interface. I don't find it intuitive. But it is by far the most popular, and one cannot argue with it's featureset, reliability and support base. And ultimately, it comes to a personal choice of what you like best. Other than that, it's a Ford vs Chevy argument, if you catch my meaning.
BlueOnyx is the open-sourced descendent of the old Sun Cobalt systems that runs on commodity hardware. It "just works", and it's completely free. And there are some big things in the works for the interface. When that happens, I think a lot of folks are going to question paying a monthly license fee for a control panel (as is the case with cPanel & Plesk).
baldeagle wrote:What are you guys talking about? I use ssh and vi.

Old school! Love it!
But back to the topic at hand...
Keith B wrote:May just be some carriers that haven't updated yet.
Keith is correct. DNS is a distributed technology, and although we (or anyone in control of DNS) can set a suggested expire time on the zones, it's ultimately up to the ISP, or if you're on a corporate network, the network admin who controls your DNS cacheing server. It's been my experience that wireless carriers tend to set their cache a bit longer in an effort to save a bit of traffic on their network. In most cases, propagation will take up to a couple hours, but there are a lot of cases where you'll see it take up to 24 hours for the cache to shake out.
In addition, the registrars can sometimes play a roll here. This is especially true when, as is the case with texaschlforum.com, the authoritative nameservers are changing. Some registrars are better than others. The company that grossed us all out last Sunday is notorious in this regard. (Well, several regards, but that one's on topic).
So hang in there, gang. If you have buddies that are still left with the old DNS cache, encourage their patience. At least it's Friday so we all have fantastic social lives and no time for the computer, right?

(Yeah, me neither...) Based on what I could tell with the migration, the results should be worth it in terms of performance.