On Fri, Jan 18, 2002 at 03:35:54PM -0500, Mike Burger wrote:
> 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.
Actually, you can do what I did and to install bind 9 and set up a split DNS.
This allows you to return different addresses based on the source address.
This would mean your DNS could return 192.168.0.1 for www.foo.com whereas for
external queries, it would return the WAN address. It works for me...
The minor downside is that all the internal hosts would have to use your DNS.
If your DNS failed and they resolved from an external nameserver, they'd get
the WAN address instead of the LAN address. Clear as mud?
.../Ed
> 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.
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
