Choosing a Namespace (Internal and External Domains?)

Discussion in 'Windows Small Business Server' started by JoeF, Mar 16, 2006.

  1. JoeF

    JoeF Guest

    I will be installing a Small Business Server 2003 Standard tomorrow which I
    have experience with in the past. This particular installation will need to
    be configured for the possibility of running Exchange server as the internet
    mail server for the company.

    I have used the .local domain extension in my past installations and
    configured Exchange's POP Connector to poll every 15 minutes to a hosted POP
    E-Mail Server such as network solutions. Initially, I will do the same for
    this installation however; what will happen down the road if we want to host
    our own e-mail server with Exchange? I realize that an MX record will need to
    be set up to point to a static IP address. I do not understand the DNS issues
    that will arise when trying to accomplish this. I guess to sum up my

    - Should my internal domain name be a subdomain of the already registered
    external domain? (Ex: "")
    - Should I just use the default SBS wizzard to name the internal domain

    Again, this will be the only server which needs to be configured with the
    possibility of running Exchange server included with SBS as the public E-Mail
    server for the company.

    I'm very confused and I have never installed Exchange as a public e-mail
    Any assistance will be strongly appreciated. Thank you and good luck to all
    of your future endeavors.


    JoeF, Mar 16, 2006
    1. Advertisements

  2. POP or MX/SMTP makes no difference.

    ..local or .lan is just fine.

    Naming of Exchange's maiboxes and how it connects and gets email doens't
    impact AD.

    You should install many more of them this way. POP was designed as a
    transition technology only.
    Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP], Mar 16, 2006
    1. Advertisements

  3. The domain name you choose for AD doesn't really matter. By default, SBS
    will suggest yourdomain.local. You can use this, or or - you just need to understand the ramifications of
    each. For example, if you use and don't make some small
    adjustments in your AD DNS, your users will not be able to find on the Internet, because your server will think it's
    entirely authoritative for and won't find www. This is not

    None of this is relevant when it comes to your Internet mail domain,
    anyway - you can run AD using mydomain.local and for
    e-mail - the wizard will prompt you for this.

    There's nothing particularly different/special about running Exchange as a
    'public' mail server - I do suggest you take a look at to understand how it works,
    but again, the SBS setup wizards (in particular, the CEICW) will help you
    set this up.
    Lanwench [MVP - Exchange], Mar 16, 2006
  4. I agree with both Susan and Lawrence in their replies but _had_ to add a
    little bit.

    There is _no reason_ for your AD DNS name to in _any way_ be related to your
    internet FQDN ( Keep up the good work of naming your AD with a
    ..local or .lan extension (I prefer .lan due to special handling some OS's
    apply to .local), the CEICW will properly configure the Exchange to handle
    email in your FQDN.
    SuperGumby [SBS MVP], Mar 16, 2006
  5. JoeF

    Russ Grover Guest

    The Special Handling of some OS's he's talking about is MAC's


    Russ Grover
    SBS2003 Remote Support
    Portland/Beaverton OR
    Email: Sales at SBITS.Biz
    Website: http://www.SBITS.Biz
    Russ Grover, Mar 16, 2006
  6. and some Linux builds, it ain't MAConly.

    SuperGumby [SBS MVP], Mar 16, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.