Go here: http://www.dnsreport.com/tools/dnsreport.c...in=thejokes.net
When I run this report on my website, I get several fails and warnings. These include:
FAILMissing (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 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
FAILMissing nameservers 2: ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns2.hostony.com.
ns7.hostony.com.
FAILStealth NS record leakage: Your DNS servers leak stealth information in non-NS requests:
Stealth nameservers are leaked [ns18.hostony.net.]!
Stealth nameservers are leaked [ns17.hostony.net.]!
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.
WARNINGSOA MNAME Check: WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: ns18.hostony.net.. However, that server is not listed at the parent servers as one of your NS records! This is probably legal, but you should be sure that you know what you are doing.
WARNINGSOA REFRESH value: WARNING: Your SOA REFRESH interval is : 14400 seconds. This seems a bit high. You should consider decreasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours, with the longer time periods used for very slow Internet connections; 12 hours seems very high to us), although some registrars may limit you to 10000 seconds or higher, and if you are using DNS NOTIFY the refresh value is not as important (RIPE recommend
WARNINGSOA EXPIRE value: WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
WARNINGMultiple MX records: WARNING: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you.
WARNINGMail server host name in greeting: WARNING: One or more of your mailservers may be 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). This probably won't cause any harm, but may be a technical violation of RFC821 4.3 (and RFC2821 4.3.1).
thejokes.net claims to be host server22.fastbighost.com.
FAILAcceptance of postmaster address: ERROR: One or more of your mailservers does not accept mail to postmaster@thejokes.net. Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.
thejokes.net's postmaster response:
>>> RCPT TO:<postmaster@thejokes.net>
<<< 550-"The recipient cannot be verified. Please all recipients of this message
550 to verify they are valid."
WARNINGAcceptance of abuse address: WARNING: One or more of your mailservers does not accept mail to abuse@thejokes.net. Mailservers are expected by RFC2142 to accept mail to abuse.
thejokes.net's abuse response:
>>> RCPT TO:<abuse@thejokes.net>
<<< 550-"The recipient cannot be verified. Please all recipients of this message
550 to verify they are valid."
WARNINGAcceptance of domain literals: WARN: One or more of your mailservers does not accept mail in the domain literal format (user@[0.0.0.0]). Mailservers are technically required RFC1123 5.2.17 to accept mail to domain literals for any of its IP addresses. Not accepting domain literals can make it more difficult to test your mailserver, and can prevent you from receiving E-mail from people reporting problems with your mailserver. However, it is unlikely that any problems will occur if the domain literals are not accepted.
=========================
I understand that the mail problems are my own to deal with. There is not much to be done there. I am a little concerned about some of the others listed. Could you please check into this?
Thanks!