• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 13247
  • Last Modified:

Configuring Exchange 2010 (Ports/DNS/Send and Receive Connectors)

I am setting up Exchange 2010 on Windows Server 2008 R2 (64-bit).  I have a domain which is controlled by dyndns.com through their "Custom DNS" service, with my router providing the updating for the dynamic dns.  Currently the server is acting as a domain controller as well as an exchange server and has IIS7 installed.

I have just done a "standard install" and have the mailbox, client access and hub transport roles installed. The current domain (dummy name) is domain.local and I want to use my domain registered with dyndns.com for the email (call it domain.com).

Couple of related questions about setting this all up:

1.  What do my DNS settings need to be. At the moment they are:

domain.com   A
domain.com  MX  10 mail.domain.com
mail.domain.com  A
www.domain.com  CNAME  domain.com
*.domain.com  CNAME domain.com

I would like anything to do with mail to use mail.domain.com (which points at my server).  I assume these DNS settings are correct?  I cannot ping the server although I can browse IIS/www.domain.com through IE so assume the DNS is set correctly.

2.  How do I go about setting up the external .com domain up in Exchange?  I have added domain.com as an accepted domain in Hub Transport (under Organization Configuration) and I have added an email address policy to use domain.com.

3.  How should I set up send and receive connectors?

4. What ports need to be open on my hardware (router) firewall and on my server firewall. The server is just using the standard Windows Firewall - I believe Exchange may have already taken care of this during installation.

I have managed to set up mailboxes for my AD users and can log into OWA.  I cannot however send or receive to those mailboxes.

Thanks in advance

1 Solution
Glen KnightCommented:
The DNS configuration looks fine, the one thing you might want to add is the autodiscover.domain.com as outlook 2007 will use this.  This should point to the same IP address as your other records.

If you have added an accepted domain and an e-mail address policy then that's all you need to do from an Exchange perspective.  Although with Exchange 2010 your receive connector by default will not accept anonymous connections which means noone will be able to send you e-mail.

To rectify this do the following, in Exchange Management Console navigate to Server Configuration > Hub Transport and right click on the connector that says Default <Servername> select properties.  Under the Authentication tab make sure only the TLS check box is checked at the top of the screen, and then under permission groups make sure anonymous users is checked.

To setup your send connectors under Organisation Configuration > Hub transport click create new send connector, it should have SMTP and address space * then set to forward to your smarthost or use DNS.

You need to configure port 25 and port 443 to be forwarded from your router to your exchange servers internal IP address.

When you say you have been able to configure mailboxes and login using OWA but cannot send e-mails can you clarify?  if you send a message from one of those users to another one does that work?
pipelineconsultingAuthor Commented:
OK - I've set up the firewalls etc. and it seems to be working to a degree.

I can send email between the mailboxes OK.  As for sending and receiving from other external email addresses I seem to be having some trouble.

When sending, my exchange server is sending me back an email saying mail sending is delayed.  I cannot receive from certain other external email addresses.

The DNS on the domain name has only been altered in the last 24 hours, so I'm guessing this is taking a while to propagate?
Glen KnightCommented:
It could take a whilte to propogate through.
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

Zacharia KurianAdministrator- Data Center & NetworkCommented:
do a lookup for you domain at http://mxtoolbox.com. then you can verify the DNS

Its possible that you have not configured Root Hints or DNS servers on the primary DNS settings.

Are you able to lookup outside addresses? Exchange may be timing out because of a DNS issue.

Also, it is not reccommended to have the Exchange doing DNS in a non-SBS scenario. I was not sure if this network was ment to be production.
pipelineconsultingAuthor Commented:
Not a production server, just testing the water.

The eventual problem turned out to be my IP was on a spam blacklist for some unknown reason!!!
I have simular issue, but with Exchange 2010 on Windows 2008 Standard server. It's also the domain server. i've done alot of tests, including telnet sending and recieving on por 25. I'm getting bounce back messages for the entire domain but all seems to be resolving correctly.

Remote host said: 550 5.7.1 Unable to relay for user@mydomain.com [RCPT_TO]

--- Below this line is a copy of the message.

Received: from [] by nm17.access.bullet.mail.mud.yahoo.com with NNFMP; 15 Jul 2011 00:04:24 -0000
Received: from [] by tm8.access.bullet.mail.mud.yahoo.com with NNFMP; 15 Jul 2011 00:04:24 -0000
Received: from [] by omp1003.access.mail.mud.yahoo.com with NNFMP; 15 Jul 2011 00:04:24 -0000
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.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now