Date: Tue, 20 Sep 2005 08:06:25 -0500 From: "Joshua Weaver" <josh@metropark.com> To: "=?iso-8859-1?Q?'Erik_N=F8rgaard'?=" <norgaard@locolomo.org>, "'steve lasiter'" <slas7713@yahoo.com> Cc: 'free bsd' <freebsd-questions@freebsd.org> Subject: RE: two questions in one Message-ID: <200509201306.j8KD6ACn022406@web.metropark.com> In-Reply-To: <432FA7FA.4080307@locolomo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd- > questions@freebsd.org] On Behalf Of Erik N=F8rgaard > Sent: Tuesday, September 20, 2005 1:11 AM > To: steve lasiter > Cc: free bsd > Subject: Re: two questions in one >=20 > steve lasiter wrote: > > My web server is up and running well and I can test > > all by going to 192.168.0.2 from any internal > > workstation, but if I try to go to www.mywebsite.com > > from any internal workstation, which maps to the > > 66.190.xxx.xxx IP directed to web server port 80 as it > > should,=20 That=92s the problem - you are using NAT, you can't "go out and come = back in", your packets will expire because they will not be routed back in, and = that's by design. You need to set up an internal forward zone in your DNS to direct requests to the internal address .To see what I am talking about, trying pinging your website from the inside using the external address. = If your router is set up appropriately, you should get a 'TTL expired' message. Set up an 'A' record for www in mywebsite.com on one of your internal = boxes to point to 192.168.0.2, and set up forwarders to your ISP's name = servers on this box. Set all your internal hosts to use that machine for DNS = requests, and you will be good to go. -Joshua Weaver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200509201306.j8KD6ACn022406>