Solved

all relevant MX records point to non-existent hosts

Posted on 2010-11-24
11
863 Views
Last Modified: 2012-05-10
We have Exchange 2007 sitting on our Server 2008 DC that receives and distributes E-Mail to all users on our network.  

Our domain is registered with and our DNS record handled by DollarDNS and we use the backup MX record service provided by www.junkemailfilter.com so that should or server go down for any reason e-mails are routed to them.  

When a major client of sends us e-mails, every now and then the e-mail will be bounced back to the sender with the message 'all relevant MX records point to non-existent hosts', but then an e-mail from them will get through.  As far as I can tell our DNS records seem to be ok, our mx record checks out ok and I am at a loss as to why these bounce backs are happening.  Could anyone help with a reason as to why this is happening or give me some other things to check?
0
Comment
Question by:simonb1975
[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
  • 6
  • 2
11 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34204364
Okay - what is your domain name?  If you post just the domain name I will hide your comment - this will allow me to give you specific advice.

Alan
0
 
LVL 10

Expert Comment

by:abhijitmdp
ID: 34204548
Run below command to find which server is accepting the mails:
nslookup -q=mx domain.com

after getting the result of the above command, try to telnet the server and post the result of the telnet.

telnet servername 25

but be sure the post 25 must be open in your firewall. Run the telnet command from outside and inside of your network.
If you find that post 25 is blocked on your network you'll need to check Firewall rules on your side; you'll need to permit Outbound SMTP on TCP Port 25 from your mail server. Check for antivirus software on the server as well, most modern AV clients block Port 25. After all this tests post the result. Also please post the full bounce back for analysis.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34204560
Okay - you have 4 MX records with priorities of 10 / 20 / 30 / 40

The ones with Priority 10 and 20 point to the same IP Address, which is pointless.  I would lose the Priority 10 MX record completely.

I can connect successfully to all IP's using telnet on port 25 - so there are no issues there.

When I connected to your own server - you are advertising yourself as server-w2008.domain.local.  Hopefully you are not configured this way on your SEND connector otherwise this will cause you mail-flow issues.

Long and the short - you don't have an MX record problems apart from the unnecessary duplicate MX record.

You do have an issue with Reverse DNS in as much as you don't have mail-gateway.domain.co.uk as your Reverse DNS record.  You should call your ISP and get them to change this (if they can).  This might cause you problems sending if you don't.

0
Transaction Monitoring Vs. Real User Monitoring

Synthetic Transaction Monitoring Vs. Real User Monitoring: When To Use Each Approach? In this article, we will discuss two major monitoring approaches: Synthetic Transaction and Real User Monitoring.

 

Author Comment

by:simonb1975
ID: 34204605
I don't want to send the full bounce back as it will reveal my customer.  How much do you need?
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34204618
Their IP Address / Domain Name should be sufficient (I will hide it again).
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34204707
I don't see any problems with the headers.  It would appear to be a DNS issue with the sending relay server for the client.

Do you want me to send you a test email?  If so - where to?
0
 

Author Comment

by:simonb1975
ID: 34205019
send to simon@mydomain.co.uk
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34205042
On the way.

Alan
0
 
LVL 76

Accepted Solution

by:
Alan Hardisty earned 500 total points
ID: 34205073
Okay - so you received my email and you replied.

This says there is not a problem with your server (or mine) so the problems have to be with the sending server - which based on the name of the domain will be like pulling teeth trying to get them to resolve it!

Ultimately - it is out of your control.  Your end is fine.  Their end is not.
0

Featured Post

Forrester Webinar: xMatters Delivers 261% ROI

Guest speaker Dean Davison, Forrester Principal Consultant, explains how a Fortune 500 communication company using xMatters found these results: Achieved a 261% ROI, Experienced $753,280 in net present value benefits over 3 years and Reduced MTTR by 91% for tier 1 incidents.

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

688 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