I've already got that going...I was just hoping to not have to use that...it'll mean having to add more virtual hosts to the apache config.
Blarg. Oh, well...thanks. On Fri, 18 Jan 2002, Dave Wreski wrote: > > > Now, however, the systems behind the firewall can't access the sites > > on the server...ie, workstation at 192.168.0.3 can't access any of the > > sites hosted on 192.168.0.1, because the DNS entries for those sites > > point them back outside the firewall...it would seem that, while the > > outside world can get through the firewall to get the sites, with no > > problem, the machines behind the firewall can't go outside the > > firewall and then back in. > > Sounds like you'll need to create a separate domain to refer to your web > server by the internal hosts, if I understand your problem correctly. > > If external users get IP-forwarded to a web server on a private IP, and > DNS has the external IP of the firewall as the public address for the web > server, then the easiest way is to in fact create a separate domain for > your internal hosts. > > Regards, > Dave > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
