Hi;
I would recommend that you seperate your FQDNs, the external & the
internal, for security reasons. However using one FQDN can be used for
both external & internal presence. You will have to configure 2 DNS
servers, and preferrably 2 firewalls. The first DNS server will be behind
the first firewall (this area of the network referred to as DMZ or
de-militarized zone). This server will handle the outside DNS requests to
access your website. The 2nd DNS server will be behind your 2nd firewall
and will handle your W2K domain resources. The 2nd DNS would be configured
to query the 1st DNS to resolve the address of the website.
Ahmed Farouk, MCSE W2K
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0014_01C12ADF.D33C42E0
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> Hello again,
> I actually sent this yesterday, but I wanted to rephrase a few things.
> When upgrading our NT Network to a 2000 Domain, we are trying to
> understand if we need to distinguish our internal network domain name
> from our external FQDN www.widgets.com. For example in NT our current
> internal domain name is "widgets" and our external website is
> widgets.com. When we upgrade to Win2k what are the ramifications of
> keeping our internal 2000 domain "widgets.com" and our external FQDN,
> widgets.com. Should we change our internal domain to widgetscorp.com or
> something comparable when we upgrade to win2k, and if we don't what
> happens. Widgets.com is currently hosted on our internal NT domain on
> an IIS 4.0 server, behind a raptor firewall, using redirection on the
> firewall, with DNS at our ISP. Once upgraded to 2000 it will continue
> to be located internally on our network behind the firewall with AD
> integrated DNS internally and external internet DNS at our ISP. Thanks
> for any help or suggestions in advance.
>
>
>
>
>
>
> ------=_NextPart_000_0014_01C12ADF.D33C42E0
> Content-Type: text/html;
> charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> <HTML>
> <HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Dus-ascii">
> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
> 6.0.4630.0">
> <TITLE>Upgrading NT Domain to 2000 Domain</TITLE>
> </HEAD>
> <BODY>
> <!-- Converted from text/rtf format -->
>
> <P><FONT SIZE=3D2 FACE=3D"Arial">Hello again,</FONT>
>
> <BR><FONT SIZE=3D2 FACE=3D"Arial">I actually sent this yesterday, but I =
> wanted to rephrase a few things. When upgrading our NT Network to =
> a 2000 Domain, we are trying to understand if we need to distinguish our =
> internal network domain name from our external FQDN </FONT><A =
> HREF=3D"file://www.widgets.com"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
> FACE=3D"Arial">www.widgets.com</FONT></U></A><FONT SIZE=3D2 =
> FACE=3D"Arial">. For example in NT our current internal domain name is =
> "widgets" and our external website is widgets.com. When we =
> upgrade to Win2k what are the ramifications of keeping our internal 2000 =
> domain "widgets.com" and our external FQDN, widgets.com. =
> Should we change our internal domain to widgetscorp.com or something =
> comparable when we upgrade to win2k, and if we don't what happens. =
> Widgets.com is currently hosted on our internal NT domain on an IIS 4.0 =
> server, behind a raptor firewall, using redirection on the firewall, =
> with DNS at our ISP. Once upgraded to 2000 it will continue to be =
> located internally on our network behind the firewall with AD integrated =
> DNS internally and external internet DNS at our ISP. Thanks for =
> any help or suggestions in advance.</FONT></P>
> <BR>
> <BR>
> <BR>
> <BR>
>
>
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm<BR>
</BODY>
> </HTML>
> ------=_NextPart_000_0014_01C12ADF.D33C42E0--
