For those of you with split DNS
( small external DNS primary for XXX.com, resolv.conf points to
internal DNS servers who are primary for XXX.com and have
forwarders to the gateway to resolve external names)
Is your firewall a network level firewall ?
So, joe_user @
yy .
XXX .
com can 'ftp foo.com' and it
connects ?
or is your firewall an application level firewall ?
So, joe_user @
yy .
XXX .
com can NOT 'ftp foo.com', they
have to 'ftp gateway.XXX.com' (TIS) or SOCKS their
way out ?
If you are application level, how do you deal with the
problem that internal mailers, network client programs, etc
can resolve A and MX records for "out there" -- but these
same client programs can NOT connect to those addresses ?
advTHANKSance
- joe
Follow-Ups:
|
|
