Marcin So�tysiak olga.pl wrote: > > I had my server moved behind a firewall and now I am having trouble > > getting Midgard to work. Do I need to use the internal ip address of > > 192.168.x.x or do I use the real ip address of 207.168.x.x? OR... Do I > > need to wait until the DNS updates with the correct IP address and just > > keep the domain name in the system instead of IP addresses? > If I see it right youir got: > > ----- --------------- > |MGD|-192.168.x.x--|Router/NAT/FW|-207.168.x.x----internet > ----- --------------- > > If so, I think u should: > > 1) set up <virtualhost www.host.com> > 2) set DNS: www.host.com IN A 207.168.x.x > 3) set NAT: 207.168.x.x <-> 192.168.x.x > 4) set MGD host named www.host.com > > AFAIK Router/NAT/FW should receive request for www.host.com and pass it to > MGD at specified internal IP but still with "www.host.com" embedded in it > (GET http://www.host.com/) so that way midgard should respond correctly.
In this case you'd still have to convince apache itself to service requests for www.host.com, which you could do by having 'order hosts, bind' in your /etc/host.conf, and then have a line mapping 192.168.x.x (whatever you picked for your server) to www.host.com. Note that you'll not be able to reach 207.168.x.x as www.host.com from that specific server. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
