AD and FQND domain

[Bob]

I will be promoting a server to an Active Directory domain
controller and wonder what the best way to handle the
following scenario is.

I already have a FQDN with webhosting for the domain
handled externally, I will not be hosting the website on
my server. For the purposes of this discussion, I will
refer to this website domain as externaldomain.com.

My intention is to promote the server and set the domain
name to externaldomain.com. My concern is when systems on
this "internal" domain try to access the webserver or mail
server hosted externally. Will the DNS forwarder send the
request to the internet domain servers if it is unable to
find the "www" or "mail" machines in it's DNS records?
Will I have to add a DNS record to point the "www"
or "mail" requests to the internet web server or external
DNS servers? What will be the best way to handle this?

Thanks.

 

[Scott Harding - MS MVP]

Make the INternal Domain name different than your real domain name. This
will save you some headaches and give another layer of security. Just make
it something like Externaldomain.local. Here's some kb's on the subject....

http://support.microsoft.com/default.aspx?scid=kb;en-us;254680

http://support.microsoft.com/default.aspx?scid=kb;en-us;285983

 

[Bob]

Thanks much!

That makes perfect sense.

Bob

-----Original Message-----
Make the INternal Domain name different than your real domain name. This
will save you some headaches and give another layer of security. Just make
it something like Externaldomain.local. Here's some kb's on the subject....

http://support.microsoft.com/default.aspx?scid=kb;en- us;254680
us;285983

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server




.

 

[Ace Fekay [MVP]]

In

Make the INternal Domain name different than your real domain name.
This will save you some headaches and give another layer of security.
Just make it something like Externaldomain.local. Here's some kb's on
the subject....

http://support.microsoft.com/default.aspx?scid=kb;en-us;254680

http://support.microsoft.com/default.aspx?scid=kb;en-us;285983

Nice links, but unfortunate they don't explain what happens and the
administrative overhead involved when you do choose the same name. At least
http://support.microsoft.com/default.aspx?scid=kb;en-us;285983 does say it's
preferred to not make them the same name, which is the general consensus.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Scott Harding - MS MVP]

True.....your right.....we've had this conversation before

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

True.....your right.....we've had this conversation before

True.. sorry.. just wanted to point that out to the poster. I think that the
KB's should be updated.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory