cyberleo2000
asked on
I am getting reverse DNS Errors when sending email
When I try to send an email to domain.com I receive the follow error:
The following recipient(s) could not be reached:
name@domain.com on 9/6/2010 2:52 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<servername.mydomain.com #4.7.1 smtp;421 4.7.1 <name@domain.com>: Recipient address rejected: No reverse DNS for 65.83.57.35. (c)
I am told the IP address referenced in the error is a netscreen router. My isp is microsoft exchange hosted services, they say they an't help me bcause its not their IP address. My exchange server is 65.83.57.34.
Can I simply add 65.83.57.35 to a reverse dns list onmy exchange server to prevent the NDRs?
The following recipient(s) could not be reached:
name@domain.com on 9/6/2010 2:52 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<servername.mydomain.com #4.7.1 smtp;421 4.7.1 <name@domain.com>: Recipient address rejected: No reverse DNS for 65.83.57.35. (c)
I am told the IP address referenced in the error is a netscreen router. My isp is microsoft exchange hosted services, they say they an't help me bcause its not their IP address. My exchange server is 65.83.57.34.
Can I simply add 65.83.57.35 to a reverse dns list onmy exchange server to prevent the NDRs?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That's what I did initially, but the email never reaches them, its being rejected before it gets to MEHS, and the IP address referenced in the eror is not my exchange server's IP address, its the IP address of a netscreen router.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The domain's mx record points to MEHS's servers. The site uses MEHS for antispam and antivirus protection. I just assumed they handled reverse dns as well. 65.83.57.34 is registered with MEHS as the exchange server. I was told 65.83.57.35 is a netscreen router. All was working ok until the site changed its default domain from ftcampbellfh.com to campbellcrossingsllc.com, this is when reverse dns errors began to appear but only when emailing brickmangroup.com. MEHS states that the reverse dns error did not come from them. that the email never eaches them. So I am now assuming the problem is in the netscreen router (which I am trying to get access too) or with DNS on the system?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
tursn out it was a problem with the ip addresses entere in mehs
ASKER