We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Cannot receive emails via Exchange 2010 - Emails are down, PLEASE HELP!

Medium Priority
1,081 Views
Last Modified: 2012-05-11
Hi, this is quite urgent, so any help would be greatly appreciated:

I have Windows 2008 R2 with Exchange 2010 installed on the same server - everything is running on this one server (including DNS, IIS, Exchange, File Server, Print Server, AD). DHCP is handled by a router. This server has fqdn: server.domain.com with local ip 10.0.0.2. The server is currently set in a DMZ. The router has port forwarding for 80, 25, 110, 993, 995, 587 and a few others all setup to forward to server, 10.0.0.2.

Exchange 2010 setup
Exchange has send and receive connectors correctly configured. I can send emails locally and externally, and can receive them locally but not externally. The receive connector is set to listen to all external ip addresses.

DNS setup
DNS is configured such that the forward and reverse lookup zones have been defined. A local cmd nslookup, cannot find server unless WINS and WINS-R are enabled. Is this supposed to happen? I thought that NetBIOS was supposed to take over?

Currently in DNS, I have:
- an A record pointing to server local ip, 10.0.0.2 (10.0.0.1 is DHCP-enabled router) and an A record pointing to external ip address of server, both linked to server.domain.com. There is also an A record on ZoneEdit - see second point for more details.
- 3 NS records, one detailing server.domain.com and the other two directing to ZoneEdit nameservers (www.ZoneEdit.com). ZoneEdit also has an A record pointing the nameservers to the external ip of domain.com. From here, the router would forward the requests/data to server.domain.com at 10.0.0.2
- a Mx record pointing locally to server, 10.0.0.2, with the fqdn set as server.domain.com.
- a CNAME record to append www as a prefix to domain.com
- a PTR record in the reverse lookup zone pointing to local server, 10.0.0.2 with fqdn server.domain.com.

local nslookup
- returns server.domain.com and its local ip, 10.0.0.2.
- set type=mx for domain.com returns the correct record in accordance with above (mail pref = 10)
- set type=ns for domain.com returns all three nameservers and their ip addresses. The ZoneEdit servers have external ip addresses listed, while the server.domain.com nameserver has the local ip listed, 10.0.0.2.
- EVEN THIS DOES NOT WORK UNLESS WINS AND WINS-R ARE NOT SETUP IN DNS

nslookup on a computer away from premesis, including online nslookup (http://network-tools.com/nslook/)
- returns domain.com and external ip address (due to ZoneEdit A record)
- set type=mx for domain.com returns nothing
- set type=ns for domain.com returns only ZoneEdit nameservers

It is as if no computer can see server, but they can see the ZoneEdit servers. However, if I type in the external ip or domain.com, the IIS7 website will load. But when I type www.domain.com, the page will not load - again this is due to servers being able to see ZoneEdit which lists an A record pointing to my external ip.

Please advise me as to what I need to do. This is quite urgent. Thank you to everyone in advance.
Comment
Watch Question

Site Reliability Engineer
CERTIFIED EXPERT
Most Valuable Expert 2011
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Hi Matt, thanks for your response.

Unfortunately, both AD domain name and external facing name are the same; domain.com.

I am heading back to the office now, and will make the changes you detailed above, and also post the screenshots. I assume you'd like to see my forward and reverse lookup zones?

I have a few questions:
1) I have a pending request with my ISP to point their rDNS records to domain.com, should I follow through with this?
2) should the mx record on ZoneEdit point to domain.com or server.domain.com?

Thanks for your help. I really do appreciate it.
tigermattSite Reliability Engineer
CERTIFIED EXPERT
Most Valuable Expert 2011
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
My domain.com is patricks.org.uk. UKPS01 is the name of my server.

Forward-lookup zone: forwardDNSZoneEdit: zoneedit
I don't fully understand what you are saying concerning the mx records. Wouldn't an A record resolving to my public IP be for domain.com, then forwarded via the router to server; not server.domain.com?
tigermattSite Reliability Engineer
CERTIFIED EXPERT
Most Valuable Expert 2011
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Matt, I can't thank you enough for the help you have provided me. The exchange server is receiving mail now. Thanks again, Steve.

Author

Commented:
Fantastic. Thank you!
tigermattSite Reliability Engineer
CERTIFIED EXPERT
Most Valuable Expert 2011

Commented:

Steve, you're welcome. Glad to hear it's working and thanks for the feedback!
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.