The reply i got was,
''Rich,
>
> When I do a nslookup on your domain it reflects a different IP then your
> servers IP.
>
> Name: twinkier.com
> Address: 54.235.159.97
> name = ec2-54-235-159-97.compute-1.amazonaws.com
>
> whois shows you have the name servers pointed to ours.
>
> Name Server: NS1.M3XS.COM
> Name Server: NS2.M3XS.COM
>
> Note: godaddy domain register allows to add additional name servers. For
> best performance please add the other two name servers.
>
> ns1.m3xs.net
> ns2.m3xs.net
> ns3.m3xs.net
> ns4.m3xs.net
>
> When I tested with the host file the site pulls up.
>
> 37.130.228.206 twinkier.com
Non-Existent Domain
>
> This file is only on server v5135l
>
>
Non-Existent Domain
>
> The internal server error you are getting is not on your server with us.
>
> This appears to be a DNS propagation issue it sometimes can take 24-48hrs
> for DNS to finish propagating.
>
> Currently the live domain is still using the amazonws IP. This is out of
> our control.
>
> Please let us know if you have any questions or concerns about this.
>
> Sincerely,
>
> Ryan''