[ale] internal net routing

[Jonathan Glass]

Do you have an internal DNS server, or hosts entries pointing to your
internal IP addresses?  If not, then your machines will try to connect
to your smoothwall's external interface, and try to NAT back in to the
server.  The server will see the connection coming from  your local IP
address (maybe) and try to send data there.  Causes all sorts of
problems.  Basically, setup an internal DNS server and make it think it
is the SOA for your domain and force your internal machines to use it
for all DNS lookups.  Also, be sure to set it to use your ISP's DNS as
forwarder servers.

GL & HTH

Jonathan

> -----Original Message-----
> From: Benjamin Dixon [mailto:beatle at arches.uga.edu] 
> Sent: Monday, August 19, 2002 6:00 PM
> To: ale at ale.org
> Subject: [ale] internal net routing
> 
> 
> 
> I've got a smoothwall box doing NAT at the office, behind 
> which is running a web server and various other services on 
> different boxen. From the outside, access to the service is 
> fine, you can go to myserver.com and get the website etc etc. 
> But from the inside, if I got to myserver.com, nothing 
> happens. I did a traceroute on it and noticed the smoothwall 
> router is where it stops, one hop, but no connection. This is 
> a problem I've run into before but never bothered figuring 
> out until now. I'm sure its an ipchains or routing issue but 
> a search on deja was fruitless. Any pointers?
> 
> Ben
> 
> 
> ---
> This message has been sent through the ALE general discussion 
> list. See http://www.ale.org/mailing-lists.shtml for more 
> info. Problems should be 
> sent to listmaster at ale dot org.
> 


---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.