HOF_Admin
asked on
Comcast and Others refusing emails (No PTR Record?)
I recently installed Exchange 2007 SP1 on A server 2008 64bit Server. I also installed a Barracuda Spam Firewall 200 on the DMz. All Mail seems to be flowing fine with the exception of a few mail servers refusing our email (shown in the Barracuda Outbound queue as deferred). We use Bluehost as our Zone records holder. I have created all the A records as instructed by bluehost.
The mail servers refusing our email seem to be Comcast, AOL, Cox.net, Juno, and a couple others. I contacted Bluehost who stated that it looked like it was a Barracuda issue. So I bypassed the Barracuda for Outbound mail. Still refused by server. I contacted Comcast who confirmed that they could not verify by rDNS.
I then Contacted Bluehost again to add a PTR record. They claim that the PTR has to be setup on our internal DNS server.
I am not sure where to turn to now. I added a PTR record to our Reverse zone look up, but not sure if I did it correctly.
Can anyone tell me how to set up the PTR Record in our internal DNS to resolve the rDNS issue?
Does this look like it may resolve the issue with the PTR record?
Do I add a PTR Record for the Barracuda External IP on our internal Domain?
HELP!!! It seems like all the members of our Board of Directors use Comcast, and our executive Director is about to have my Head on a Platter.
The mail servers refusing our email seem to be Comcast, AOL, Cox.net, Juno, and a couple others. I contacted Bluehost who stated that it looked like it was a Barracuda issue. So I bypassed the Barracuda for Outbound mail. Still refused by server. I contacted Comcast who confirmed that they could not verify by rDNS.
I then Contacted Bluehost again to add a PTR record. They claim that the PTR has to be setup on our internal DNS server.
I am not sure where to turn to now. I added a PTR record to our Reverse zone look up, but not sure if I did it correctly.
Can anyone tell me how to set up the PTR Record in our internal DNS to resolve the rDNS issue?
Does this look like it may resolve the issue with the PTR record?
Do I add a PTR Record for the Barracuda External IP on our internal Domain?
HELP!!! It seems like all the members of our Board of Directors use Comcast, and our executive Director is about to have my Head on a Platter.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Only your ISP (internet service provider) can set rdNS for your IP address. If this is the new IP address, I also suggest you to check the blacklisting as well to avoid the problem in future. You can check it from the following URL:
http://www.mxtoolbox.com/blacklists.aspx
http://www.mxtoolbox.com/blacklists.aspx
ASKER
Thank You for all your replies,
Blacklist are clear.
Our DNS Zone records are managed by Bluehost, but AT&T is our ISP. I just sent a request to AT&T since Bluehost says everything is good on their side. We will see if AT&T can help.
Thanks Again!
Blacklist are clear.
Our DNS Zone records are managed by Bluehost, but AT&T is our ISP. I just sent a request to AT&T since Bluehost says everything is good on their side. We will see if AT&T can help.
Thanks Again!
Once your ISP sets rDNS, you will have to allow few hours for the propagation of rDNS.
ASKER
Ok, so now bluehost claims that they do not add custom pointer records at this time. So i will be transferring our DNS to AT&T. Once i Get this accomplished i will divvy out the points for the solution....
I find it really hard to believe that there are no other Blue Host clients that have exchange in-house.
Update:
All is well after moving our DNS hosting to AT&T. I have added the pointer and even before updating the name servers for our website on Bluehost, Comcast and several others that were previously refusing our email began accepting. AOL took an extra day even though I used the AOL Postmaster tool and was able to verify that rDNS was working.
It was really helpful to have Experts-Exchange members assistance to confirm the correct solution while attempting to have a third party make the changes necessary.
I find it really hard to believe that there are no other Blue Host clients that have exchange in-house.
Update:
All is well after moving our DNS hosting to AT&T. I have added the pointer and even before updating the name servers for our website on Bluehost, Comcast and several others that were previously refusing our email began accepting. AOL took an extra day even though I used the AOL Postmaster tool and was able to verify that rDNS was working.
It was really helpful to have Experts-Exchange members assistance to confirm the correct solution while attempting to have a third party make the changes necessary.
http://mxtoolbox.com/diagnostic.aspx - here you have great mail server diagnostics tool, where test and verify the server has a reverse DNS (PTR) record too.