Here is the output for dig
You should only have one IP address entry for whitehorse12.com. This should be your web server IP address only.
# dig whitehorse12.com
;; ANSWER SECTION:
whitehorse12.com. 6679 IN A 188.8.131.52
whitehorse12.com. 6679 IN A 184.108.40.206
;; AUTHORITY SECTION:
whitehorse12.com. 6679 IN NS host.whitehorse12.com.
whitehorse12.com. 6679 IN NS ns15.zoneedit.com.
whitehorse12.com. 6679 IN NS ns13.zoneedit.com.
You have host.whitehorse12.com listed as a DNS server, but this server isn't listening on DNS port 53 as seen by the telnet test. Proof also comes from the fact that this host isn't responding to DNS queries at all for whitehorse12.com. If it is not a DNS server, it needs to be removed form the NS server list.
The other listed NS servers don't have listings for www.whitehorse12.com.
There are entries for whitehorse12.com on the zoneedit servers. But it is returning two IP addresses. The first, 220.127.116.11, is the IP address of a zone edit DNS server, not your webserver IP address. There shold be only one entry listed. I suspect the correct entry should be 18.104.22.168.
# host www.whitehorse12.com ns15.zoneedit.com
Using domain server:
IP address 22.214.171.124 is listening on port 80 and has Apache running. This is probably your web server. I get a 200 OK message when doing a curl head command.
# host whitehorse12.com ns15.zoneedit.com
Using domain server:
whitehorse12.com has address 126.96.36.199
whitehorse12.com has address 188.8.131.52
whitehorse12.com mail is handled by 0 mail7.zoneedit.com.
whitehorse12.com mail is handled by 0 mail6.zoneedit.com.
Using curl to get the entire contents of the page gives a blank. So it looks like the website isn't running as a virtual host using just the IP address.
# curl -I 184.108.40.206
HTTP/1.0 200 OK
Status: 200 OK
Expires: Wed, 22 Oct 2008 06:02:44 GMT
Date: Tue, 21 Oct 2008 06:02:44 GMT
Content-Type: text/html; charset=ISO-8859-1
Curl specifying the URL whitehorse12.com gets a proxy prompt, which is probably the correct website you have running.
# curl 220.127.116.11
If you fix the name server issues listed, then you should be able to get it all to work.
# curl -U whitehorse12.com 18.104.22.168
Enter proxy password for user 'whitehorse12.com':