Solved

Exchange 2010 cannot send to specific domain

Posted on 2013-11-04
7
468 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
  • 4
  • 3
7 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
Comment Utility
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
Comment Utility
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
Comment Utility
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
Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
Comment Utility
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
Comment Utility
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)
Comment Utility
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
Comment Utility
Agreed thanks.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

771 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now