Setup DNS for internal users but keeping namespace same for ext us

[Guest]

I'm at a startup comp tasked with setting up a new network.
The Windows Server 2003 running Apache SW is at the owners home.
The developers and QA staff work out of there homes or the office.
Everyone uses DNS name to access the server from their remote locations or
the office.

The plan is to bring the server into an office suite locating it behind a
firewall and a switch. In doing this, make the necessary IP changes to the
server reflecting a secure static non-public IP address behind the FW
(10.x.x.x) with the WAN port being a public IP address available for
incomming WAN users. Internal users will be served private DHCP (served via
FW) when using the office network.

My question is, can I setup an internal DNS name (pocket.case.com) to
reflect the public DNS name also (pocket.case.com) so when developers and QA
are on the office network, they can still access (pocket.case.com) server
without sending data past the switch and firewall to the public DNS and
coming back in? Yet the public still has access to the public DNS via the
Public IP via rule on the firewall to the private IP address on the internal
network.

To make this happen, I would plan on using the two NIC's in the server, one
bound to the public IP address and the other bound to the internal IP
address. Is there something I am missing? Can I add a DNS service on the
2003 server without requiring additional hardware?

My goal is to allow seemless communication for staff no matter where they
maybe sitting, home or in the office, yet provide the best security possible
while still building the startup business without having lots of cash.

Your wisdom and support are always greatly appreciated!

Thanks,
Jeff

 

[Guest]

Hi There

Why not locate the server in a DMZ. give it one public IP address. Configure
the firewall with the relevent rules to protect the server whilst allowing
the access needed. e.g. prehaps allow windows RDP connections from inside
the LAN to the DMZ, but only port 80 WWW access from the Internet to the
DMZ.

Andy

 

[Guest]

Thank you for your response.
For equipment, I have one FW and one switch. The Win2003 SE is running only
Apache, no IIS, no domain, no DNS.
When in the office, I want the data traffic to be limited between
PC-switch-server, without having to go out to the FW and a public DNS thus
bogging down the 1.5mb IN-pipe traffic serving incoming requests for clients
and home users.

Without having extra equipment to play and test, I can only rely on research
and opinions of the much more experienced network engineers.

thanks.

 

[Guest]

What is the firewall make and model? Many firewalls have a DMZ function.
Even my home ADSL one does!

 

[Guest]

Netgear
FVS
124G

What is the firewall make and model? Many firewalls have a DMZ function.
Even my home ADSL one does!