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

rDNS problem

Quick rundown:  we recently migrated exchange and DNS servers, I don't think this has much to do with the problem.  Our domain's MX records point to a 3rd parties IP that filters spam for us then forwards cleared messages to one of our public IPs.  Our outbound SMTP traffic goes out of the same public IP the 3rd party forwards to, but there is obviously no MX record.  

Now we are starting to get blacklist/HELO bounce back errors from a few domains.  This has everything to do with our outbound SMTP and MX records being different, no?  Do we pretty much have to unify the IPs or is there some work-around?
0
PatGroupIT
Asked:
PatGroupIT
  • 5
  • 3
1 Solution
 
redseatechnologiesCommented:
Hi PatGroupIT,

Have you got a PTR record for you IP address?

What is you domain so we can have a look and test it out?

-red
0
 
PatGroupITAuthor Commented:
Yep, we have a PTR record set up on our internal DNS server,  but it doesn't have an external address or NAT or anything.  The domain is patinagroup.com
0
 
redseatechnologiesCommented:
Your internal DNS server?

What is your external IP address?

Your domain looks fine so far...

-red
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
PatGroupITAuthor Commented:
Yep, DNS server with a private address and no public.  External for smtp outbound is 64.161.229.131...different than the MX record.
0
 
redseatechnologiesCommented:
This could be the problem,

There is a reverse DNS entry for that IP, but that does not have a corresponding A record

http://www.dnsstuff.com/tools/ptr.ch?ip=64.161.229.131

Get your ISP to create an entry that matches the PTR record

-red
0
 
redseatechnologiesCommented:
... or change the PTR record to match your servers real name (that it has an A record for)
0
 
PatGroupITAuthor Commented:
Might this new A record conflict with the DNS entry for the website (hosted at yet a 3rd outside IP)?
0
 
redseatechnologiesCommented:
>Might this new A record conflict with the DNS entry for the website

It shouldn't, but your DNS looks to be of an "interesting" configuration.

Ask the ISP and see if they can create an A record that matches the reverse lookup - that will not affect the website in any way at all

-red
0
 
cjtramanCommented:
Check if your ISP collecting email on your behalf has PTR record configured for your email domain.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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