• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1567
  • Last Modified:

Reverse PTR Record

I have a client that we need to email that is in Slovenia. When we attempt to send them an email we get a bounce back saying our email was not delivered due to security policies with mailhub.siol.net reporting:

"Recipient address rejected: Blocked - Your IP [XX.XXX.XXX.XXX] has no corresponding reverse (PTR) address. Ask your Internet Service Provider to assign you IP with valid reverse (PTR) record. ##"

I use Comcast as my ISP and have asked for a Reverse PTR record. I have gone to DNSStuff and executed a Reverse PTR check and it has come back that this IP Address points to my server of Mail.domain.com

Any thoughts on what to try next?
0
bturnerpcg
Asked:
bturnerpcg
  • 2
  • 2
2 Solutions
 
netcmhCommented:
Wait. DNS entries take time to propagate all around the world.
0
 
rawinnlnx9Commented:
Reverse pointers and SPF records and such must be defined wherever your domain is registered. So on go daddy you need to go into domain tools and edit your domain settings. This is where your mail server was defined, your mx records and such.

Who is your domain registrar? If you are hosting your own using something like PLESK even better.

Here's a better explanation:
http://www.itworld.com/networking/362601/how-setup-reverse-dns-and-ptr-records
0
 
rawinnlnx9Commented:
DNS entries do not take hours. This is a reverse lookup. Your message recipient server looks at the mail header and sees "Oh this came from 126.28.234.10" and then it thinks cool. Now I want to verify that this is a legitimate domain correctly configured to send email. It says hey what's your reverse PTR and it wants to see 10.234.28.126 in the reply. Soon as you have that set up it's instant. You also need to make sure your IP is not blacklisted by them or any other server. DNS stuff has tools to do this.

DNSStuff should see that your PTR is your mail servers IP but backwards.
0
 
bturnerpcgAuthor Commented:
Not a waiting game as we did this about a week ago. I am looking a little more closely and it appears my request was pointing to the wrong server name. Making the corrections now.
0
 
netcmhCommented:
Ah, information that could have been helpful earlier. Good luck.
0
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.

Join & Write a Comment

Featured Post

How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now