> I had a similar problem, and it turned out to be a DNS issue.
>
> It appears that BQ checks for an authoritative DNS resolver
> for a requested
> domain, and redirects the viewer to the IP provided by the
> authoritative
> resolver.
>
> So if www.somedomain.com exists somewhere else and you are
> moving it to a BQ
> server, you need to create www2.somedomain.com on the BQ
> server as an alias,
> and the DNS server pointing to the BQ server.
Domain/site didn't exist until I started it on here. DNS is hosted by
EasyDNS so I am not using DNS on the server locally, and I know DNS is
working properly because I can run a dig on an external Linux box and it
returns the correct IP address.
From another email...
>What happens when you do
># service httpd restart
The service stops and restarts without error. Same thing if I do 'service
network restart'.
The fact that I can connect to the systems from other PCs on the same subnet
is most perplexing... If I were not able to connect at all, I would be
better suited to troubleshoot this. The fact that PCs locally can hit the
sites by FQDN, or IP, and sites external can't, is very frustrating. These
are good suggestions, but ones I have already tried. What is also
troubling, is that the site was working fine, and then one day it wasn't.
Unfortunately, considerable time had passed between those dates so I don't
know when it really stopped working as I was doing my stuff on a local
system.
Thanks everyone for your suggestions though. I'll keep plugging away at
this.
Ernie
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.