-----Original Message-----
From: Fred Viles <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, May 11, 1999 4:35 PM
Subject: [Masq] Re: please help with ipportfw
>
>On 11 May 99, at 11:52, David A. Ranch wrote about
> "Re: [Masq] please help with ipport":
>
>|...
>| FTP needs the special FTP module and to have port 20 forwarded as well.
>
>I thought this too at first, but there is no need to set up port
>forwarding for port 20. The FTP masq module sets up masq entries for
>data ports as needed.
All is working now, and I did NOT added a forwarder for port 20.
>
>|...
>| >Because there
>| >is an external DNS name mapping to the external IP, internal clients
using
>| >the external DNS will have to connect to the external IP as well, being
>| >forwarded to the internal NT box.
>|
>| You should have two DNS zones. One for external IPs and one for internal
>| IPs.
>
>Either two zones on the same server, with the internal zone using a
>non-standard TLD (like company.cxm instead of company.com). Or,
>better yet, run a separate server for the internal zone. Your public
>server publishes only the names you want the world to know about with
>their public IPs, while your internal server's zone files include
>*all* your hosts and their intenal IPs.
I maintain my zone at The Public DNS. So what you're talking about is to
run a DNS server on my masq box specifically for internal machines, which
would serve the same names as at The Public DNS but point to internal IP's?
Derek
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
