Of course this blatant dns issue must be at hand, I should have
originally said "Verfiy dns resolution and look at your logs to see if
dns requests are being blocked".
Tom Eastep wrote:
>Jerry Vonau wrote:
>
>
>>I''ll bet that apache can''t resolve it''s own
virtual hostnames, with the firewall
>>inplace, outbound dns request maybe blocked, while without the firewall,
>>the lookups complete. I''ll guess the hosts file may not be
setup for the virtual
>>hosts, on the webserver. If you want to have apache resolve for the
connecting
>>ip, then you''ll have to allow the traffic from the webserver to
a dns server
>>anyway.
>>
>>
>>
>
>And that server must resolve the ip address of the Apache host to the
>correct external DNS name(s).
>
>-Tom
>--
>Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
>Shoreline, \ http://shorewall.net
>Washington USA \ teastep@shorewall.net
>PGP Public Key \ https://lists.shorewall.net/teastep.pgp.k
>
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click