You need to contact your ISP and have them correct the error. Basically the previous IP owner was suing "mail.flodynecontrols.com" on this IP and they never removed it or changed it.

We are flodynecontrols.com. What exactly do I tell Verizon about this issue? And what is 127.0.0.2?

You can call them and ask to setup a reverse DNS record for mail.flodynecontrols.com that points to a proper IP address. (65.254.254.52). Usually it may take anywhere from 24-72 hrs for the change to replicate around the world. Also ask them to remove any other IP addresses currently pointing to your subdomain.

They did the Reverse DNS record last month. The error message says:
WARNING: Forward-DNS does NOT match Reverse-DNS.

How do we get the forward to match the reverse?

Forward DNS points to an IP address (example.com -> 10.10.10.10), while reverse DNS point to a domain name (ie 10.10.10.10 -> example.com).

I just did a quick test for the domain name (http://www.dnsstuff.com/tools#dnsReport/type=domain&&value=flodynecontrols.com&&) there may be more problems than just the IP/domain name mismatch

And another one for rDNS (http://www.dnsstuff.com/tools#ipInformation/type=domain&&value=65.254.254.54&&)

mail.flodynecontrols.com has few IP addresses,

DNS Records – FLODYNECONTROLS.COM
Record      Type      TTL      Priority      Content
flodynecontrols.com      A      1 hour            38.113.20.14 (Boston, MA, US)
flodynecontrols.com      MX      1 hour      30      mail.flodynecontrols.com
mail.flodynecontrols.com      A      1 hour            65.254.254.50 (Burlington, MA, US)
mail.flodynecontrols.com      A      1 hour            65.254.254.53 (Burlington, MA, US)
mail.flodynecontrols.com      A      1 hour            65.254.254.55 (Burlington, MA, US)
mail.flodynecontrols.com      A      1 hour            65.254.254.52 (Burlington, MA, US)
mail.flodynecontrols.com      A      1 hour            65.254.254.54 (Burlington, MA, US)
mail.flodynecontrols.com      A      1 hour            65.254.254.51 (Burlington, MA, US)
flodynecontrols.com      NS      1 hour            ns2.purehost.com
flodynecontrols.com      NS      1 hour            ns1.purehost.com
flodynecontrols.com      SOA      1 hour            ns1.purehost.com. admin.purehost.com. 2010081345 10800 3600 604800 86400
flodynecontrols.com      TXT      1 hour            v=spf1 ip4:38.113.1.0/24 ip4:38.113.20.0/24 ip4:65.254.224.0/19 ?all
*.flodynecontrols.com      A      1 hour            38.113.20.14 (Boston, MA, US)


At least one is correct, the other ones should be removed if are invalid. You may need to contact Pure Host support to have them change it as they are controlling them.

have you set up a @ and mail text record with your domain controller.

also see
http://help.dnsmadeeasy.com/domain/reverse-dns/

not sure who your ISP is but this may be helpful it is for time warner

http://www.twcbc.com/NYC/HelpSite/ResourceItem/how-to-create-a-ptr-record.ashx

Here's the thing. We use a web hosting company that gets all our incoming emails. Our server uses Exchange and the Pop3 connector to retrieve the email from our web hosting place. We use exchange to send emails as well. So I am not sure how to answer your question....

Your ISP is verizon, which provides a public IP address for your office connection.
Your hosting company Pure Host provides hosting space and email services. They also provide public IP addresses and subdomains.

mail.flodynecontrols.com may exist at the web hosting provider, and let's say the IP address assigned to it should be 1.1.1.1

Verizon provides 5 public IP addresses, 2.2.2.2 is the gateway and 2.2.2.3 is the exchange server (exchnage.flodynecontrols.com)

The proper DNS settings should be:
mail.flodynecontrols.com             A             1.1.1.1
exchange.flodynecontrols.com     A             2.2.2.3

reverse dns
1.1.1.1             PTR          mail.flodynecontrols.com
2.2.2.3             PTR          exchange.flodynecontrols.com

Those entries should be present in network solutions and pure host. Depends on your contract with Pure Host they may be able to help you troubleshoot it.

I've requested that this question be deleted for the following reason:

Solutions proposed too complicated for me to implement.......