Link to home
Start Free TrialLog in
Avatar of arikin
arikin

asked on

Apache2 and server's new domain

I just changed a debian (Etch4.04) test server over to production.  The domain and IP address were changed on a separate DNS server's namedb/ns records (Our own name servers).  On the debian server "uname -a" correctly brings up the new domain.

Problem: The domain does not work in a browser (time out).  The connection is refused (via a command line on another server).

What else should be set up for apache2 on Debian 4.04 to use the new domain?
ASKER CERTIFIED SOLUTION
Avatar of edster9999
edster9999
Flag of Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of arikin
arikin

ASKER

Thanks for covering all the bases so well.  This turned out to be a firewall.  The IP was being filtered at the gateway switch level because the previous server's settings were still there.
Thanks again.