Cc: 'Cristian Salan'; 'Gelsema, Patrick';
freebsd-questions@freebsd.org
Subject: Re: natd or firewall problem?
Gelsema, Patrick wrote:
Thats right, you can do the following:
Put the ip-address with its FQDn
(www.webserverwhatever.com) in every
hosts file (taken its windows
Hello dear list,
I have one FreeBSD router in front of the internal network. Now I've
installed another FreeBSD box which must be the www sever.
I've managed to redirect the port 80 at the router and the web server
is visible to the outside world. But the problem is now at the other
internal
Hi,
IN order to enlighten you we need some more information. Sounds to me you
could be having issues with internal/external DNS and ip-addresses. In
other words, you are querying your www server from a dns and is getting
the Internet ip back instead of the lan ip. Can you connect to your www
Hello dear list,
I have one FreeBSD router in front of the internal network. Now I've
installed another FreeBSD box which must be the www sever.
I've managed to redirect the port 80 at the router and the web server
is visible to the outside world. But the problem is now at the other
,
Patrick
-Original Message-
From: Cristian Salan [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 05, 2005 1:51 PM
To: Gelsema, Patrick
Cc: freebsd-questions@freebsd.org
Subject: Re: natd or firewall problem?
Hello dear list,
I have one FreeBSD router in front
On Sat, 5 Feb 2005 13:54:23 +0100, Gelsema, Patrick
[EMAIL PROTECTED] wrote:
Thats right, you can do the following:
Put the ip-address with its FQDn (www.webserverwhatever.com) in every hosts
file (taken its windows) or in its hosts file on freebsd. Or you run an
internal DNS with an internal
Gelsema, Patrick wrote:
Thats right, you can do the following:
Put the ip-address with its FQDn (www.webserverwhatever.com) in every hosts
file (taken its windows) or in its hosts file on freebsd. Or you run an
internal DNS with an internal zone for your domain whilst running on the
internet the
