Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Im starting to learn Exchange on my own, kind of a side project. I recently purchased 2 domains from godaddy to play around with it. The 2 domains that I own are and

I dont really want to call this is an issue but more of someone being able to either give me instructions how to host my exchange email on my server at home or give me step by step instructions.

Currently, I have a server up running Server 2008 R2 with exchange 2010 on it. I havent updated it yet, so it has no service packs or anything yet. As I stated above, I currently have 2 domains hosted by godaddy. The one im trying to setup email with is

Currently, inside my godaddy dns I have an mx record "@" and then an A record that has pointing to my home external IP which is hosted by ATT Uverse.

After this is where im completely confused. I essentially have exchange setup to send email externally by reading a few articles and what not but my DNS setup isnt complete. Where im confused I guess is what do I add to the internal DNS on my home server. And is my godaddy DNS properly configured?

Also, I cannot access my OWA from the outside, could you guys please help me get that accessible from the outside as well? I really appreciate all the help. I hope this is enough information, if its not I will be more than happy to provide more.



share|improve this question

closed as not a real question by Mathias R. Jessen, Ward, Jenny D, Bryan, Dave M Apr 24 '13 at 12:30

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

You've already had one home related question closed as off topic, so you should know that this question is off topic too. But just in case you haven't read the FAQ yet, I'd suggest you do so. – Bryan Apr 24 '13 at 11:36

You don't need to add anything to the internal DNS on your home server. shows your DNS is OK and SMTP connections to your server are at least partly working (firewall OK).

You need to configure Exchange to not drop the connection (follow the MXToolbox link and click the SMTP test link), I can't guess why it's doing that.

Configure Exchange to answer email for those two domains, add a recipient policy or add the email addresses to your user account. Sounds like you are nearly there.

Follow the Exchange 2010 Deployment Assistant: and/or install checklist here

Also, I cannot access my OWA from the outside, could you guys please help me get that accessible from the outside as well?

For a start, your server is not answering on port 443 (HTTPS). Check your firewall / router / port forwarding settings. Then Windows firewall. Then IIS configuration - is it listening on port 443? Then Exchange Outlook Web Access configuration (does it work on the LAN?) will do a more thorough job than any of us could, although it can't check OWA directly, if you can get Outlook Anywhere / Exchange Activesync connecting from it, then OWA will stand a good chance of working, too.

share|improve this answer
Thanks for the help, I will see what I can do to fix these issues. For the OWA, dont I need to add a record to the godaddy DNS? I have no record of anywhere, that is my OWA address. – Mike K Apr 24 '13 at 2:20
If you have an SSL certificate for it, you will need a DNS entry for the SSL Certificate address so it works properly. But it should be accessible and workable using https:// IP /owa or https:// /owa albeit with an SSL warning about a name mismatch. If you use self-signed SSL or are testing with the default certificate, it won't make much real difference. If you have a single SSL cert, then you will need an internal DNS A record for IP:internal IP. With a SAN certificate, you could put the server's hostname in for internal use. Lots of options! – TessellatingHeckler Apr 24 '13 at 2:30

Not the answer you're looking for? Browse other questions tagged or ask your own question.