New Exchange Server Next Steps

Hello,
      I have a brand spanking new network running Server 2012. It also has Exchange 2013. The network is up and running and is healthy. It consists of only two servers, the DC and the server running Exchange. It is for a small business environment. Probably 5 users total. I wanted to use Office 365 but the owner is not budging on having his own Exchange server. I have a Comcast Business Internet connection with a static ip. The private network domain is , let’s say, anydomain.local. The registered domain I have at godaddy is anydomain.us. Now that this is all in place what are the next steps to get the Exchange server online? I know this is a broad question but I am hoping that perhaps a broad answer may get me up and going.

Thank you
LVL 1
daskas27Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Eprs_AdminSystem ArchitectCommented:
Hi,

you have to go to your DNS Portal and combine your domain with one of your external IP´s

mail.anydomain.com -> external IP
0
Eprs_AdminSystem ArchitectCommented:
Have you setup the send connector and receive connector in exchange ?
0
daskas27Author Commented:
No to both.When you say DNS portal do you mean the DNS server? I have the DC running DNS.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Muhammad MullaCommented:
You will need to setup an mx record with your anydomain.us provider from their portal to point to your external IP and configure your firewall to forward emails to your exchange server. You will also need to setup send and receive connectors in exchange as mentioned above.
0
daskas27Author Commented:
I have setup the send connector and receive connector. I am a little confused on the DNS Portal.
0
Eprs_AdminSystem ArchitectCommented:
Have you setup your mx records in your dns server ?
Please check if you have mx records in your DNS server zone
0
Muhammad MullaCommented:
If I, as an external person, need to send an email to daskas27@anydomain.us, there will be a DNS lookup for an mx record in the anydomain.us hosts file. This is managed by whoever hosts the DNS (externally) for the domain anydomain.us. Normally you can manage this yourself through a portal of some sort.

You need to create the record type MX and point it to an external IP address of your exchange server.
0
daskas27Author Commented:
Ok. That I understand.
0
daskas27Author Commented:
Please see attached. Does this look correct? I am confused as the private network domain is nofinishline.local and the registered domain at godaddy is nofinishline.us. Is this a concern?
DNS_MX_Redacted.pdf
0
daskas27Author Commented:
Anybody? I am dead in the water here.
0
Muhammad MullaCommented:
@ is not a valid character that you can use in DNS
0
Muhammad MullaCommented:
The Internet standards (Requests for Comments) for protocols mandate that component hostname labels may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen ('-'). The original specification of hostnames in RFC 952, mandated that labels could not start with a digit or with a hyphen, and must not end with a hyphen. However, a subsequent specification (RFC 1123) permitted hostname labels to start with digits. No other symbols, punctuation characters, or white space are permitted.
0
daskas27Author Commented:
I am afraid I do not understand. I modeled this after another network that I work with and that is what they had.
0
daskas27Author Commented:
If I ping email.nofinishline.us it does see the external IP that I updated the records with.
0
it_saigeDeveloperCommented:
@OfflineGeek - The OP doesn't have a choice on the '@' symbol usage.  This is how GoDaddy has their DNS manager setup so that @ represents an alias for the domain - nofishline.us.

@Daskas - Your MX record setup is redundant.  If one record becomes unavailable, they are both unavailable.  You only need one of these (does not matter which one).

-saige-
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
daskas27Author Commented:
@it_saige - So if I understand you correctly I am good with these settings?
0
it_saigeDeveloperCommented:
Looks good, personally I would change a couple of things.

1.  Remove this entry:Capture.JPG
2.  Change the SPF record from -
"v=spf1 mx:smtp.nofinishline.us mx:email.nofinishline.us ip4:96.91.90.214"

Open in new window

To -
"v=spf1 mx ip4:96.91.90.214 ~all"

Open in new window

-saige-
0
daskas27Author Commented:
Thank you. Will do.
0
nashim khanExchange AdministratorCommented:
Hi,

You can follow the below link FYI.

http://www.petenetlive.com/KB/Article/0000716.htm
0
daskas27Author Commented:
Thanks to all.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.