Posted on 2005-04-18
Last Modified: 2010-04-18
I wonder if someone can help.

I have just set up a new AD and just realised I have set it as a domain.local instead of

Therefore in control panel it says the domain is local.

What effect will this have, and how can i change it to
Question by:alanheaton
    LVL 7

    Expert Comment

    There is no problem if your AD domain is .local, it is even recomended to have your internal AD domain as company.local, and the external, intenet domain as, the only problem is that your internet web server should be external, and you will need also an external DNS, from your ISP.
    This way if your internal and external domains are different, your users will not be confused about what resources are internal and what are external.

    If you still want to rename it,
    You ca use the domain rename tool from Microsoft to rename a 2003 domain,

    But if you have just created the domain, you haven't configured anything yet, then the easyest way is to demote the DC , this will delete your domain and everything in AD, and promote it to the new domain.
    LVL 2

    Author Comment

    I am not planning on running a web server. The AD is only for interrnal use, I may install Exchange at some stage but this will be OK.

    Access to the web is via a router which is then connected to a switch.

    This should be OK then.

    Do i need to change anything, because I have already setup up all the users and file server.
    LVL 7

    Accepted Solution

    You can leave it this way, from the security point of view this is the way to do it!

    Expert Comment


    I've setup MS SBE and configured the internal domain as payperbox.local and the external domain is, however the exchange server is having problems receiving external emails. I can send external and internal emails as i'm using my ISP's SMTP server and i can receive internal emails. The web server for the domain is external as mentioned above and i've also put in the ISP's DNS servers as alternate DNS servers, if the internal server cannot resolve any DNS queries.

    The MX record is pointing to, which is a Host (A) record created just for the server on the domains hosting control panel. This (A) record is pointing to the clients single static IP address, which is assigned to the external side of their wireless router. The router is configured to pass all SMTP,POP3,IMAP,HTTP,VNC and REMOTE ACCESS requests to the internal IP address of the server

    what have i dont wrong or not done, to cause the problems i'm currently having.

    I've noticed a couple of thinks, in system manager the recipient update service is showing the domain as payperbox.local IS THIS CORRECT or does this need to show the external domain.

    Also i checked the MX record on and there is the following error: " ERROR: I could not complete a connection to any of your mailservers! " under the MX Record - Connect to mail servers row.

    Please Help

    LVL 2

    Author Comment

    what you need to do is acouple of things.

    a) At your isp, you have set up your (a) record to point to your static IP. That is correct if you want to host your own web site or use your web address for OWA or exchange extras. You will need to creat a subdomain of your external domain name at your isp. Then in your MX record get it to point to your sub domain. eg '' then in your sub domain set the (a) record to your static IP. Also in your MX record of set the Prio to 10 which should be your lowest number so it uses that server first.

    b)You need to set up a recipient policy for Go into Exchange System Manager. Under Recipients click Recipients Policy, then in the right hand pane you should see default policy. Right click default policy and then click properties. Click 'E-mail address Policy' then add.
    Select smtp and then put '' That should sort it

    Any probs let me know


    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Join & Write a Comment

    It is a known fact that servers reach the end of their lives. Some get there quicker than others, based on age, manufacturer, usage and several other factors. However, if your organization has spent time deploying Microsoft's Active Directory server…
    Learn about cloud computing and its benefits for small business owners.
    Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
    This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

    745 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now