Hab diese Ausgabe erhalten. Ich kann leider mit dem ganzen net sonderlich viel anfangen.
NS
INFO
NS records at your nameservers
Your NS records at your nameservers are:
ns6.nameserverservice.de. [TTL=259200]
ns5.nameserverservice.de. [TTL=259200]
PASS
All nameservers report identical NS records
OK. The NS records at all your nameservers are identical.
PASS
All nameservers respond
OK. All of your nameservers listed at the parent nameservers responded.
PASS
Nameserver name validity
OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASS
Number of nameservers
OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
PASS
Lame nameservers
OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
PASS
Missing (stealth) nameservers
OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
PASS
Missing nameservers 2
OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.
PASS
No CNAMEs for domain
OK. There are no CNAMEs for domainname.tld. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. Note that I only checked domainname.tld, I did not check the NS records, which should not have CNAMEs either.
FAIL
No NSs with CNAMEs
ERROR: I checked with your nameservers to see if there were any CNAMEs for your NS records (there shouldn't be), but they all timed out.
PASS
Nameservers on separate class C's
OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.
INFO
Nameservers versions
Your nameservers have the following versions:
217.172.161.234: No version info available (reports a format error; likely a broken DNS server).
217.172.162.55: No version info available (reports a format error; likely a broken DNS server).
SOA
INFO
SOA record
Your SOA record [TTL=2560] is:
Primary nameserver: ns6.nameserverservice.de.
Hostmaster E-mail address: hostmaster.domainname.tld.
Serial #: 1073043000
Refresh: 16384
Retry: 2048
Expire: 1048576
Default TTL: 2560
PASS
NS agreement on SOA serial #
OK. All your nameservers agree that your SOA serial number is 1073043000. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS Report only checks the NS records listed at the parent servers (not any stealth servers).
PASS
SOA MNAME Check
OK. Your SOA (Start of Authority) record states that your master (primary) name server is: ns6.nameserverservice.de.. That server is listed at the parent servers, which is correct.
PASS
SOA RNAME Check
OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is:
hostmaster@domainname.tld. (techie note: we have changed the initial '.' to an '@' for display purposes).
WARN
SOA Serial Number
WARNING: Your SOA serial number is: 1073043000. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.
WARN
SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 16384 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; 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 86400 seconds if using DNS NOTIFY). This value determines how often secondary/slave nameservers check with the master for updates. A value that is too high will cause DNS changes to be in limbo for a long time.
PASS
SOA RETRY value
OK. Your SOA RETRY interval is : 2048 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
PASS
SOA EXPIRE value
OK. Your SOA EXPIRE time: 1048576 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). 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.
PASS
SOA MINIMUM TTL value
OK. Your SOA MINIMUM TTL is: 2560 seconds. This seems normal (about 60 to 86400 seconds or 1-24 hours is good). RFC1912 2.2 recommends 1-5 days (86400 to 432000) unless you are about to change DNS entries. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
MX
FAIL
MX Category
ERROR: I couldn't find any MX records for domainname.tld. If you want to receive E-mail on this domain, you should have MX record(s). Without any MX records, mailservers should attempt to deliver mail to the A record for domainname.tld. I can't continue in a case like this, so I'm assuming you don't receive mail on this domain.
Mail
FAIL
Connect to mail servers
ERROR: I could not find any mailservers for domainname.tld.
WWW
INFO
WWW Record
Your
www.domainname.tld A record is:
www.domainname.tld. A 62.112.153.49 [TTL=86400]
PASS
CNAME Lookup
OK. Some domains have a CNAME record for their WWW server that requires an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. There are no CNAMEs for
www.domainname.tld, which is good.
Allerdings ist im nameserver tool ein MX record vorhanden.
Ist halt dieses Tool von Server vor Free.
MFG
CHRIS
)