Well ... this is embarrassing. But I've ranted and raged about it so loudly and often ... and so many of you have willingly given your time and effort ... the least I can do is suck it up.
That whole Apache thing ... I have this firewall blocking my private traffic from the world. The server which houses Apache has only private addressing. And the firewall passes traffic destined for a certain IP to that server. For example, any traffic destined for 216.63.139.129 is routed to the server's private IP address.
In my httpd.conf, I had the following:
<VirtualHost 216.63.139.129:80>
ServerName exitwound.org
ServerAlias exitwound.org *.exitwound.org
...
</VirtualHost>
<VirtualHost 192.168.5.7:80>
ServerName exitwound.org
ServerAlias exitwound.org *.exitwound.org
...
</VirtualHost>
Obviously, I have Apache configured to serveral virtual hosts with only one IP. The purpose of the dual entries was to serve requests from the Internet and also for requests originating from the private network.
What I overlooked was the firewall/router issue. The firewall receives the request for the external and translates it/routes it to the internal. The Apache server doesn't know anything about the external IP address.
All of the changes I have been making over the past several days have been only to the externally-addressed VirtualHost entry. Yeah. The entry that will never be used.
Thanks again to everyone who pitched in.
Man ... what a dumbass ...
Posted from exitwound.org, comment here.
