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

Reverse DNS Configuration Exchange 2010

Hello,

We recently set up our network. I must admit this is a new "land" for me. I am more a Software developer, not a Network Administrator but I had to get hands on the problem.

Some email providers, are rejecting our emails. AOL among others are complaining about server with no reverse dns. I found pretty good articles online about it but i have still some doubts and i want no chances when it comes to our live system.

This is my scenario.

I have my Domain Controller server (DC001), Exchange Server (EXC001) and i have like 10 different domains (for email addresses) like john.doe@zzzz.com, john.doe@yyyy.com, john.doe@xxxxx.com. All of them pointing to the same user in our Active Directory. My domain in the network is ATL.LOCAL

I understand i have to set an A record witm mail.????, a MX record and PTR record... but where exactly?

Should i add these records to my MAIN domain (ATL.LOCAL) or should i add one for every mail domain i am using? mail.zzzz.com, mail.yyyy.com, mail.xxxx.com. My feelins are that i have to add them to each and every domain i might be sending emails from... right?

Please, help. Thank you so much.
0
acampos
Asked:
acampos
  • 3
  • 3
  • 2
  • +2
2 Solutions
 
sunnyc7Commented:
Call your ISP and ask them to setup a PTR record for your external FQDN - mail.domain.com > to your public IP

Check your present config.
www.mxtoolbox.com
enter your domain name
click smtp diagnostics

if you get - reverse DNS doesnt match SMTP banner > then call ISP.

thanks
0
 
jorlando66Commented:
The reverse dns should be set with your isp.  It should resolve the address that your smtp server announces itself as.  What is happening for example say your mail server announces itself as mail@yourdomain.com but the public IP that your isp hosts resolves to serverport@yourisp.com this will fail reverse dns.

Contact your ISP and have them add the rdns for you.
0
 
SiborgRaiderCommented:
Set these in the dns control panel of your domain name, you can ask your isp to setup a rdns for you.
0
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

 
jorlando66Commented:
lol.  I could use the ^^^^ again sunny
0
 
sunnyc7Commented:
ha ha :)
0
 
pr0t0c0l12Commented:
from what you are describing, you only need to create the A + MX on hte primary domain controller (if it is using DNS/DHCP on the same server). your john.doe@zzzz.com will also have to have contacts to host the different domains under his account. You would have to create contacts like john.doe@yyyy.com, and john.doe@xxxx.com.  All this settings should be applied to atl.loca. IT will be a very complicated solution but have one domain controller manage all the accounts and if they need to have access to the AD, use delegation permissions to add each AD Domain Controller to read from atl.local

Good luck.
0
 
acamposAuthor Commented:
@Sunnyc7
I went to mxtoolbox.com. I typed in like 5 of our domains. they all came back good BUT when i click on the SMTP Test i get all Green Dots except for Reverse DNS

Green - Not an open relay.
Green - 0 seconds - Good on Connection time
Yellow - 5.273 seconds - Warning on Transaction time
Red - Reverse DNS FAILED! This is a problem.
Green - OK - Reverse DNS matches SMTP Banner

@pr0t0c0l12 Thank you for your response. i think that's what i have to do. Yes, i do have one domain controller managing all the accounts. Each user has their corresponding domains assigned.

@all the people... thank you for your inputs. I am gonna try right now and i will let you know as soon as i can.

Greetings.


0
 
acamposAuthor Commented:
One more thing

Session Transcript:
HELO please-read-policy.mxtoolbox.com
250 XXXXXXX.ATL.LOCAL Hello [XX.XX.227.133] [47 ms]
MAIL FROM: <supertool@mxtoolbox.com>
250 2.1.0 Sender OK [47 ms]
RCPT TO: <test@example.com>
550 5.7.1 Unable to relay [5070 ms]
QUIT
221 2.0.0 Service closing transmission channel [47 ms]


maybe this can help a lil bit.
0
 
sunnyc7Commented:
Yeah thats good > it should not be able to relay >> since your server is *not* an open relay :)
0
 
acamposAuthor Commented:
Ok. this is what i did (and i guess it will take a little bit of time before it replicates all over)

I went to my DC server.

opened up DNS
expanded SERVERNODE
expanded Forward Lookup Xones
expanded ATL.LOCAL
added a Host(A) with my MX external server IP
added a (MX) record

nothing is happening so far when i check in nxtoolbox.com but i guess it takes some time.

now remember i have a lot of other zones at the same level than my domain name ATL.LOCAL that matches most of my email domains (@yyyy.com, @xxxx.com, etc)...

ok. Is there anything else i should check in the meantime?
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

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