Re: Point me in the right direction??

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Kevin D. Goodknecht [MVP] (admin_at_nospam.LSAOL.COM)
Date: 03/02/04


Date: Tue, 2 Mar 2004 14:57:57 -0600

In news:7ir940tb6loa9m20c4lb55otgivi1n49va@4ax.com,
Robert M. Cepek <rcepek@sbcglobal.net> posted a question
Then Kevin replied below:
> Hello all
>
> Over the past few days I have seen some great discussions on internal
> vs. external names. So in regards to that I have a question on
> which would be the best way to configure DNS & AD.
>
> Would it be a better choice to use the name chemical.com or
> chemical.mfg? My original thinking was to use chemical.com but now
> I'm second guessing myself on using chemical.mfg, as this would cause
> less headaches in the management side? We would be hosting our own
> website and email, and just wanted to see what the guru's thought? and
> to see if my thought process was online or went BSOD?
>
> Rob

You can use either name, chemical.mfg would be easier if you don't have a
full grasp on setting up a DNS zone. Chemical.com would cause less confusion
for internal users since you will be hosting a website and email locally,
and in the long run it will be easier to manage. If you are going to host
websites and email locally you will need a local zone for chemical.com so
you can access the sites by that name.
Keep in mind if you currently have an external website and mail server using
chemical.com, you will have to add records to access those sites.
If you are going to use exchange, using chemical.com will make that setup
easier since Exchange adopts the Active Directory domain name as its default
email domain. If you use chemical.mfg the Exchange setup will use that name
as the default domain for email. So you would still have to set exchange up
to accept mail for chemical.com.

-- 
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
-- 
When responding to posts, please "Reply to Group"  via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
 http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
 http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
 http://www.oehelp.com/OEBackup/Default.aspx
==========================================


Relevant Pages

  • Re: win2003 & exchange 2003 mail problem
    ... Have a look in IIS Manager under the Default Exchange website, ... > I have a win 2003 enterprise edition server with one domain, ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 ActiveSync, Sprint PPC-6700 and SSL: Giving me a
    ... > certificate, but once you've got it working it just continues to work. ... Both Exchange and the Exchange OMA virtual ... >>> My certification path was the same www.mydomain.com that my website uses ... When I look at IIS in Server Management, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and a ISPs Exchange and Sharepoint
    ... While I was discussing the website the programmer mentioned that he ... was intergrating exchange into it. ... feratures to intergrate sharepoint. ... choice either to use hosted Exchange or use your own Exchange within SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and a ISPs Exchange and Sharepoint
    ... Actually the companyweb in SBS is used ... While I was discussing the website the programmer mentioned that he ... was intergrating exchange into it. ... feratures to intergrate sharepoint. ...
    (microsoft.public.windows.server.sbs)
  • Re: URGENT - LOGIN PROBLEMS
    ... Look at the logs in X:\WINNT\SYSTEM32\LOGFILES\W3SVC ... Exchange doesn't care about URLs - only IIS does. ... This posting is provided "AS IS" with no warranties, ... >>I'd bet it is going to the wrong website. ...
    (microsoft.public.exchange.admin)