[support] Gone live problem

[Jamie Holly]

First thing to do - make sure that your computer is going to the correct 
IP. From a command window:

nslookup example.com

If the IP is right then check your server error logs. A 500 error is not 
a DNS error. It actually comes from a webserver (see RFC 2616). As long 
as you are going to the right server, then the big hint will lie within 
the server's error logs.

Also make sure you have a CNAME set up:

example.com. A xxx.xxx.xxx.xxx
www.example.com. CNAME example.com.

You need to CNAME www. to your A record or it won't work since www. is 
viewed as a subdomain. This wouldn't lead to the error (you would just 
get a server not found error - no HTTP error codes), but it does prevent 
future problems of people who want to use the www.

Jamie Holly
http://www.intoxination.net
http://www.hollyit.net


On 6/18/2012 10:46 AM, Joel Willers wrote:
> I was referring to his hosts file on his personal machine for testing. Editing your hosts file makes you not have to wait for DNS changes, as you're telling your browser what IP address it supposed to be used. I use it to see what happens if I want a site to go live but what to see the ramifications first.
>
> Joel
>
>
> -----Original Message-----
> From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On Behalf Of Earnie Boyd
> Sent: Monday, June 18, 2012 9:40 AM
> To: support at drupal.org
> Subject: Re: [support] Gone live problem
>
> On Mon, Jun 18, 2012 at 8:44 AM, Joel Willers wrote:
> >  You can always change your 'hosts' file on your machine to test how something works without actually changing the A record. Just add a line with IP address and the URL you want it to take over. Just make sure you remove it, otherwise you might not notice problems in the future.
>
> I don't believe the OP has access to his /etc/hosts file and the provider will not do it for him.
>
> --
> Earnie
> -- https://sites.google.com/site/earnieboyd
> --
> [ Drupal support list | http://lists.drupal.org/ ]