553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)

Yes. Here is what it returned. Please let m know what needs to be done to rectify it. Also, on the name servers they are referencing an ISP I don't use anymore. Should my current ISP provide me with information to replace this?

Open DNS Servers

ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are:

Server 207.103.0.14 reports that it will do recursive lookups. [test] Server 207.103.11.9 reports that it will do recursive lookups. [test] See this page for info on closing open DNS servers.

Missing (stealth) nameservers

FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly.

ns3.voicenet.com.
ns4.voicenet.com.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).

Stealth NS record leakage

Your DNS servers leak stealth information in non-NS requests:

Stealth nameservers are leaked [ns3.voicenet.com.]!
Stealth nameservers are leaked [ns4.voicenet.com.]!

This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.

Here are the errors in the Mail section:

WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

monmouth.voyantinc.com claims to be invalid hostname
'*l7********************************ESMTP':
   220 *l7********************************ESMTP

(Voyant is the spam filtering service we use at all sites)

ERROR: One or more of your mailservers does not accept mail to postmaster@timesonline.com. Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.

monmouth.voyantinc.com's postmaster response:
>>> RCPT TO:<postmaster@timesonline.com>
<<< 554 5.7.1 <postmaster@timesonline.com>: Recipient address rejected: User not registered with ContentCatcher

WARNING: One or more of your mailservers does not accept mail to abuse@timesonline.com. Mailservers are expected by RFC2142 to accept mail to abuse.

monmouth.voyantinc.com's abuse response:
>>> RCPT TO:<abuse@timesonline.com>
<<< 554 5.7.1 <abuse@timesonline.com>: Recipient address rejected: User not registered with ContentCatcher

Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).

These are all of the warnings and errors in the Mail section of the DNS test.

Good stuff. I ran the URL and it came up with a different IP address then the external one given to me by the ISP. I am having a rDNS record added for this address and will let you know how it goes.