550 Invalid RDNS entry

I have a client that says he is getting a bounceback when sending a message to our domain

mail.summit-inc.net rejected your message to the following email addresses:
alfred@st-inc.net (alfred@st-inc.net)
mail.summit-inc.net gave this error:
Invalid RDNS entry for 6.7.8.9

I went to DNSSTUFF.COM and looked up the rdns for our domain and it looked correct.  

9.8.7.6.in-addr.arpa.      PTR      IN      3600      41ms      co*****.com.


Is there  another reason why the clients message would get rejected?  I don't really understand the whole rdns thing in the first place so I guess it could very well be incorrect!
NytroZAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

upalakshithaCommented:
Hi,
It is not clear to me, but i can say you this. sender's server ip should have a correct PTR (RDNS) entry setup.
If alfred@sc-inc.net is the sender mail.summit-inc.net should have a proper PTR (RDNS) Eentry.
If co****.com is sender then, mail.co****.com should have proper PTR RDNS entry setup.
Thank you
0
footechCommented:
If someone is getting rejected by your domain, it should be their PTR record which needs to be corrected.

Depending on email filtering settings, a receiving server can look at the IP of the incoming connection and check whether there is a PTR associated with the IP.  Further it could also check to make sure the name returned by the PTR record has an A record that references back to the same IP.  This is a spam prevention feature as most dynamically assigned IPs won't have a PTR record.
0
Amit KumarCommented:
Can you provide your domain name to check PTR records.

or you can do it via mxtoolbox.com

PTR's domain name and MX name should be the same in this case.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

upalakshithaCommented:
Hello,

you need to check sender's PTR (RDNS) record in order to resolve this. this happens sender's host name does not have a proper RDNS entry setup. when you receive a mail from external domain your mail server checks from where it comes & if it does not match RDNS of sender's host name it will be rejected from your mail server. but the sender you specify here will not possible to send mail to almost all mail servers in the world if it has issues with RDNS entry. you can check this with them.

thanks.
0
NytroZAuthor Commented:
The domain name is context4.com.  We dont' have any RDNS issues with anyone else but this single domain we are sending to.
0
NytroZAuthor Commented:
This is the record that is coming back.  Why is this incorrect?  


13.94.90.96.in-addr.arpa.      PTR      IN      3600      41ms      context4.com.
0
footechCommented:
You need to be clear.  First you said there was a problem with receiving email from a client on another domain, then you said there was a problem sending to another domain.  Which is it?
0
NytroZAuthor Commented:
I apologize....our employee is getting an error sending to the client.  The error states that or rdns is incorrect

Context 4.com cannot send to summit.com
0
footechCommented:
I don't believe I've ever seen multiple PTR records for a single IP before, so I couldn't say if that could cause any issues.
I think the domain you're sending to is doing a forward-confirmed reverse DNS check.  If the IP resolves to "context4.com", "context4.com" doesn't resolve back to the same IP.  Instead your PTR record should point to "mail.context4.com", which I see you have an A record for which points to the same IP.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Amit KumarCommented:
your PTR is as below:

PTR      96.90.94.10      context4healthcare.com      60 min
PTR      96.90.94.10      context4.com      60 min

and your MX record is as below mentioned:

mail.context4.com      96.90.94.10      30 min      Blacklist Check      SMTP Test

create one PTR for mail.context4.com with IP 96.90.94.10
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.