Dnsstuff Hataları

FAIL 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 DNSreport will not query these servers, so you need to be very careful that they are working properly.
pdns3.ultradns.org.
pdns2.ultradns.net.
pdns1.ultradns.net.
pdns6.ultradns.co.uk.
pdns5.ultradns.info.
pdns4.ultradns.org.
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).

FAIL Missing 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:
udns1.ultradns.net.
udns2.ultradns.net.

FAIL Stealth NS record leakage Your DNS servers leak stealth information in non-NS requests:
Stealth nameservers are leaked [pdns6.ultradns.co.uk.]!
Stealth nameservers are leaked [pdns5.ultradns.info.]!
Stealth nameservers are leaked [pdns4.ultradns.org.]!
Stealth nameservers are leaked [pdns3.ultradns.org.]!
Stealth nameservers are leaked [pdns2.ultradns.net.]!
Stealth nameservers are leaked [pdns1.ultradns.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.

WARN SOA MNAME Check WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: dns-external-master.amazon.com.. However, that server is not listed at the parent servers as one of your NS records! This is legal, but you should be sure that you know what you are doing.

WARN SOA REFRESH value WARNING: Your SOA REFRESH interval is : 600 seconds. This seems low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.

WARN SPF record 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).