|
Posted by Leythos on April 4, 2006, 4:00 pm
If you were Registered and logged in, you could reply and use other advanced thread options
mike.cocker@hotmail.com says...
> Question: Will users still be able to access the web/email/ftp server
> internally/externally from intranet.companyname.com (web),
> mail.companyname.com (mail), ftp.companyname.com (ftp) or the static IP
> address? If so, how does that work? If not, how do I grant them access?
If your DNS resolves to the proper IP Address then they should be able
to reach it.
So, if you have the server on a 192 scheme, and you are on a 192 scheme,
then you need DNS records for the public names on your internal DNS
server that point to the 192 addresses of the services. You would keep
the public IP DNS for people outside the local network and just forward
the ports inbound to the services IP address.
So, if the server was at 192.168.10.10 on the LAN and your PUBLIC IP was
244.12.12.12 you would need the following:
Public DNS A record 244.12.12.12 intranet.companyname.com
Public DNS A record 244.12.12.12 mail.companyname.com
Public DNS A record 244.12.12.12 ftp.companyname.com
PRIVATE DNS A record 192.168.10.10 intranet.companyname.com
PRIVATE DNS A record 192.168.10.10 mail.companyname.com
PRIVATE DNS A record 192.168.10.10 ftp.companyname.com
Your internal network clients should point to your internal DNS server
so that they resolve the internal IP's as defined.
Some devices allow DNS loopback, but not all, in that case you would not
need the Private DNS entries.
--
spam999free@rrohio.com
remove 999 in order to email me
| 
XML site map