Talk:Bad httpd conf
What other possibilities for fixing this exist, except for talking to your friendly tech support team? :) I have now 3 new sites exhibiting this very same issue, and in spite of several attempts to recreate them, the error remains. --Gwyneth Llewelyn 10:37, 20 Oct 2006 (PDT)
- Bad httpd conf is the error produced when the apache server is not properly configured to accept the website in question.. there are a lot of reasons this can happen, but none of them are particularly common, and almost all of them require tech support. If you are managing your own DNS, you may want to query our name server (ns1.dreamhost.com) for the correct IP address as it may have changed. All other variations of this problem (such as an actual misconfigured server) can only be resolved by contacting tech support.
- This condition can sometimes appear and resolve itself within a day or so naturally, if you did anything that would change your IP address (such as adding a unique IP or SVN service to a domain.) Good luck! -- Sabrejack 10:46, 20 Oct 2006 (PDT)
This never happens when I use godaddy as the registrar. It only happens when I use Bluehost as a registrar and forward the DNS to Dreamhost. It almost feels like I'm being penalized for using a hosting competitor as a domain registrar, though I'm sure this is not the case. I cannot help but wonder if it's more likely a bug in DH's DNS system with regards to certain types of domain registrar. I wonder if most other people with similar problems are also using hosting competitors like Bluehost or Hostgator, etc., as a domain registrar.
It's great that they've invented an 'error code' to discern the problem. Since DH invented their own error code, they could even put a link to this wiki on the error code page. Better, could DH please fix the problem so it resolves automatically after it's detected? --Greenman 08:17, 28 January 2011 (PST)