As quoted from this thread:
“… bad_httpd_conf errors in general mean that something interfered with the generation of your site’s entry in our Apache web server configuration file. You can sometimes work around this yourself by editing your domain from the web panel, ‘submitting’ it (even with no changes), and waiting a bit. This forces it to be re-generated, which may work. Obviously the error shouldn’t happen in the first place, but if you want to get the site up ASAP this can sometimes help.”
But if they really meant DNS, what propably happened is they switched your IPs. If example.com resolved to 127.0.0.1 today, and I changed the DNS to point to 127.0.0.2 instead, it will take time for people to get routed to 127.0.0.2. But the web server listening on 127.0.0.1 will not be configured for example.com anymore, and thus will spit out this error page when people using old DNS info try to access http://example.com. Or it could also be the DNS has propagated, but the web server is not configured yet.
Either way, it may be a matter of time, trying to “edit” the web service as above, or contacting support.
Perl / MySQL / HTML CSS