Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Exchange 2010 cannot send to specific domain

Posted on 2013-11-04
7
Medium Priority
?
492 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)
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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 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

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Question has a verified solution.

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

The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Suggested Courses

782 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