Re: Setup DNS for internal users but keeping namespace same for ex
- From: <andy_cafferkey@xxxxxxxxxxx>
- Date: Wed, 28 Sep 2005 10:31:05 -0000
What is the firewall make and model? Many firewalls have a DMZ function.
Even my home ADSL one does!
"JPRICE" <JPRICE-please@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FF075FB7-DFEF-489D-A5D6-BC960648E71D@xxxxxxxxxxxxxxxx
> 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.
>
>
>
> "andy_cafferkey@xxxxxxxxxxx" wrote:
>
>> 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
>>
>>
>> "JPRICE" <JPRICE@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:7EC09F03-AE3C-445A-9C8F-CAFD1FAC204C@xxxxxxxxxxxxxxxx
>> > 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
>>
>>
>>
.
- Follow-Ups:
- References:
- Re: Setup DNS for internal users but keeping namespace same for ext us
- From: andy_cafferkey
- Re: Setup DNS for internal users but keeping namespace same for ex
- From: JPRICE
- Re: Setup DNS for internal users but keeping namespace same for ext us
- Prev by Date: Re: Q: Script to append the exisiting DNS suffix search order on
- Next by Date: Re: Difference between DNS CName record and Domain Name Server?
- Previous by thread: Re: Setup DNS for internal users but keeping namespace same for ex
- Next by thread: Re: Setup DNS for internal users but keeping namespace same for ex
- Index(es):
Relevant Pages
|