+ Reply to Thread
Results 1 to 5 of 5
  1. Google Ninja jibbajabba's Avatar
    Join Date
    Jun 2008
    Location
    Ninja Cave
    Posts
    3,314

    Certifications
    TechExam Certified Alien Abduction Professional
    #1

    Cool .local vs top level domain

    We are having a bit of an argument here.

    When would you give AD a .local domain and when a top level domain ?

    Obviously .local isn't routeable .. but in that particular case it doesn't have to.

    Basically there is one Server which supposed to run Exchange (also acting as domain controller) and one webserver which will be joined to the domain.

    The exchange server will host one domain which ie. example.com .. and the webserver will host the website example.com

    Now - would you name the actuall AD example.com or example.local ?
    Last edited by jibbajabba; 01-16-2009 at 10:05 AM.
    Reply With Quote Quote  


  2. Login/register to remove this advertisement.
  3. Google Ninja jibbajabba's Avatar
    Join Date
    Jun 2008
    Location
    Ninja Cave
    Posts
    3,314

    Certifications
    TechExam Certified Alien Abduction Professional
    #2
    Reply With Quote Quote  

  4. Senior Member
    Join Date
    Mar 2007
    Posts
    12,320
    #3
    It's typically a best practice to give the internal domain a different name than the external name. There's a variety of ways to do this. You could make it a child domain, such as ad.company.com, or you could give it a different suffix such as company.local or company.corp. Like you said, you'll probably have some trouble using those on the internet. However, why would you want your AD traffic on the internet? You should be using VPNs or something else to connect to other internal networks. As far as Exchange goes, I believe you can create a mapping or something from your external domain to your internal domain, so that will work transparently and seamlessly. I'm sure Royal will be able to elaborate.
    Reply With Quote Quote  

  5. New Member royal's Avatar
    Join Date
    Jul 2006
    Location
    Chicago, IL
    Posts
    3,373
    #4
    Quote Originally Posted by dynamik View Post
    I'm sure Royal will be able to elaborate.
    So with Exchange, if you're using the same domain name for AD and external, not really much you have to do on Exchange. If you're using different domain names, you'd create an Accepted domain which matches your external namespace and then create an e-mail address policy so it assigns users this external namespace and have it mark that namespace as their Primary SMTP Address. Pretty simple.

    And yes, I'm also a fan of having your AD name different. .local or a subdomain of your internet namespace that isn't used externally that will be your forest root domain. You can always create a regular primary dns zone that matches your external namespace should you have the need for Split-Brain DNS.
    Reply With Quote Quote  

  6. Senior Member
    Join Date
    Feb 2008
    Location
    West Yorkshire, UK
    Posts
    269

    Certifications
    A+, N+, 70-270, 70-290, 70-291, 70-293, 70-294, 70-298. MCSE 2003! 70-620
    #5
    It can be anything too. thiscompanyis.mine for example.

    It's purely there to stop internal traffic from routing to the outside world i.e. .co.uk .com etc. etc.
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks