WARNING: Your nameservers do not include any corresponding A records when asked for your NS records. They probably are not returning the A records when asked, which can prevent some other DNS servers from contacting your DNS servers. They should do this if they are authoritative for those A records. The problem record(s) are:
Nameserver [ip_do_meu_server] did not provide any IPs
-------------------------------------------------------------------------------
WARNING: Your nameservers report somewhat different answers for your NS records (varying TTL, for example).
-------------------------------------------------------------------------------
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 will not query these servers, so you need to be very careful that they are working properly.
ns1.shopodonto.com.br.shopodonto.com.br.
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).
-------------------------------------------------------------------------------
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:
sp.linkbr.com.br.
ns1.shopodonto.com.br.
--------------------------------------------------------------------------------
FAIL: Your DNS servers leak stealth information in non-NS requests:
Stealth nameservers are leaked [rj.linkbr.com.br.]!
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.
---------------------------------------------------------------------------------
ERROR: Your nameservers disagree as to which version of your DNS is the latest (2006011202 versus 2006011204). This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 2006011204 is the correct serial #. The serial numbers reported by each DNS server are:
200.196.254.164 # ip da link-br: 2006011202
[ip-do-meu-servers]: 2006011204
-----------------------------------------------------------------------------------
ERROR: Your SOA (Start of Authority) record states that your master (primary) name server is: localhost.. However, that is not a valid domain name!
------------------------------------------------------------------------------------
WARNING: Your SOA EXPIRE time is : 36000 seconds. This seems very low. You should consider increasing 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.
-------------------------------------------------------------------------------------
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). This probably won't cause any harm, but is 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.
mx.shopodonto.com.br claims to be non-existent host shopnet.com.br:
220 shopnet.com.br ESMTP "Versao nao disponivel"
---------------------------------------------------------------------------------------
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).