Scenario breakdown on help with Mail Server and PTR records.

This month the IT staff in the company left our company without any notice. I'm now once again back in trying to resolve some major mail problems. A great number of our companies emails are not reaching hosts such as AOL, Comcast etc... After looking around I suspect a PTR issue and even more I believe our Email server was never setup with proper DNS records. I'm not in anyway ready to figure this out myself so I would like help getting our servers setup with correct DNS and PTR records. I will break down our system design in detail. Currently webmail is enabled under as the only method of mail access.

Domain Name is hosted by 3rd party provider.
1 In house AD Domain Controller setup newerafinance.local
1 In house exchange server setup on the same network as DC.
        LAN Network is on
        WAN Network is on
Go to To View TCIP config image.

Domain is registered and host records are setup with
To view current records please go to

Public nslookup with mx records show..

Non-authoritative answer:       MX preference = 10, mail exchanger =       nameserver =       nameserver =       nameserver =       nameserver =       nameserver =  internet address =  internet address =  internet address =  internet address =  internet address =

As you see Im not sure where to start looking to resolve the DNS issues and setup PTR but from the looks up things it seems as the network was never finished with proper settings. What I also see as a problem is that the domain points to the 3rd party host provider but yet the mail server is in house therefore setting up PTRs is not simple for me.

Who is Participating?

Improve company productivity with a Business Account.Sign Up

Chris DentConnect With a Mentor PowerShell DeveloperCommented:


IP Configuration:

Members of Active Directory Domains (and Domain Controllers) should never reference DNS Servers that cannot answer authoritatively for the AD Domain.

In the picture posted we see the external interface has two external DNS Servers listed. These need to be removed, if you wish to use them they should be added as Forwarders under the DNS Console on the server.

Having these present will cause authentication failures and policy application problems.

MX Record:

This one is absolutely fine.

Mail Server:

Does mail send out directly from the mail server? Or is it relayed?

If it's sent out directly there are two things to do:

1. Check the name.

Check the name in the properties for the Send Connector (Organisation Configuration) in Exchange System Console.

It should be a public name, ideally because that's what's used in the MX.

2. Check NAT / PAT

NAT (Network Address Translation) and PAT (Port Address Translation) are important, you need to know which IP Address your server is using to connect to others.

This isn't always the same as the IP Address it uses to accept inbound connections.

If the network only has a single public IP, or you haven't changed it from the default it will be using the (external) IP of the router / firewall.

3. Reverse Lookup

Your Reverse Lookup Record need to be configured for the IP used for the server as discussed in 2.

It we assume that it matches the IP used for inbound that means you need a Reverse Lookup Record added like this:  PTR

Your ISP will have to add that for you, it's not something you do on your own DNS Service as you don't have authority for the range.

bashyywashAuthor Commented:
1. fixed the TCPIP settings for the Domain Member Exchange server to only use the AD DNS. Added the WAN DNS servers to the DC Forwarders.

2. The Exchange send connector did not have ANY FQDN associated with it, so I added

3. Company owns a Block of IP's. Default network is on (public ip on smoothwall firewal)
and Exchange server WAN on SO I ASSUME is used for incoming emails and is used for outgoing emails. Therefore i will need to ask Internet Provider to add  PTR ?

Are the A Record and C.Names done correctly?

Images added for reference.
bashyywashAuthor Commented:
OR wait since the WAN is the Only gateway then outgoing is also, RIGHT ?
Chris DentPowerShell DeveloperCommented:

> wait since the WAN is the Only gateway then outgoing is
> also

Provided NAT is operating for both Inbound and Outbound connections for the server. Any sensible setup would have it configured for bi-directional so it's very probably safe to assume it has been.

The FQDN you've added is great, that just means you need the PTR with the IP:  PTR

As above, that must be added by your ISP etc :)

All DNS records in the Forward Lookup zone associated with the MX and Exchange (for outbound) are absolutely fine.

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.

All Courses

From novice to tech pro — start learning today.