Solved

Exchange 2010 cannot send to specific domain

Posted on 2013-11-04
7
476 Views
Last Modified: 2013-11-05
Hi Folks,

We cannot send messages to a single domain.  (blueblanket.com)
When I run nslookup for the domain I get the following output.  
We are getting an incorrect mx record ip address returned.  I called the remote host IT staff and they said the mx record ip address for remote host mail.blueblanket.com should be:

64.206.15.19

The it staff at the remote host do not recognize fe.mail.blueblanket.com and they say it is invalid.  Flushing the caches on both the domain controller and the exchange 2010 server are ineffective.  

What is the best course of action to resolve this.  The rest of outbound mail is good.  I was thinking of creating a custom send connector for this domain but wanted to check first.  Seems like a dns glitch.  Our mail server is configured to use external dns.

Regards,
Richard

C:\>nslookup
Default Server:  our local domain controller.com
Address:  10.0.1.15

> set type=mx
> blueblanket.com
Server:  our local domain controller.com
Address:  10.0.1.15

Non-authoritative answer:
blueblanket.com MX preference = 10, mail exchanger = mail.blueblanket.com
blueblanket.com MX preference = 20, mail exchanger = fe.mail.megapathdsl.net

fe.mail.megapathdsl.net internet address = 66.80.60.33
0
Comment
Question by:rjearley1966
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39622352
The result you are getting is also what I can see.
Do you use forwarders in your AD DNS settings? It could be that it is cached somewhere else.

Simon.
0
 
LVL 1

Author Comment

by:rjearley1966
ID: 39622400
Yes Simon,

Forwarders on DC1 & DC2 are set to three external:

64.7.11.2          Megapath
66.80.131.5      Megapath

Use root hints is checked.   Where else could it be cached.  

Interestingly we have the same isp "Megapath".
0
 
LVL 1

Author Comment

by:rjearley1966
ID: 39622432
I have no evidence to support this but I just have a feeling it is tied to us being with the same isp (Megapath).  Thinking we are getting some bad cached mx record replies for them so I added google 8.8.8.8 as the first dns server on each of the domain controllers and the the messages cleared the Exchange 2010 queue.

I hate fixes that do not give me a clear understanding of why something happened.  

Megapath btw has been a great isp.  Have had them for ten plus years with zero production downtime.  Routine maintenance at 1:00 1:00 am periodically of course.  Started with them on sdsl and now on Business Ethernet.
0
Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39624843
If you have forwarders enabled, then the use Root Hints doesn't come in to it.
When forwarders are enabled, little information is being cached, so it is come from upstream.

You could try doing an NSLOOKUP against their servers directly to see what the results are - if they are wrong then the problem is with the ISP.

Simon.
0
 
LVL 1

Author Comment

by:rjearley1966
ID: 39625004
I got these results Sembee2:  

C:\>nslookup
Default Server:  UnKnown
Address:  192.168.1.1

> server 66.80.130.23
Default Server:  ns1.megapath.net
Address:  66.80.130.23

> set type=mx
> blueblanket.com
Server:  ns1.megapath.net
Address:  66.80.130.23

blueblanket.com MX preference = 20, mail exchanger = fe.mail.megapathdsl.net
blueblanket.com MX preference = 10, mail exchanger = mail.blueblanket.com

blueblanket.com nameserver = ns2.megapath.net
blueblanket.com nameserver = ns1.megapath.net

fe.mail.megapathdsl.net internet address = 66.80.60.33
ns1.megapath.net        internet address = 66.80.130.23
ns2.megapath.net        internet address = 66.80.131.5
>
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39625065
That pretty much proves the point - the ISP has an issue. Could be they have different servers for clients than the internet and one of them is incorrect. Alert the ISP as they need to fix it.

Simon.
0
 
LVL 1

Author Comment

by:rjearley1966
ID: 39625074
Agreed thanks.
0

Featured Post

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses

617 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