bettwaesche-spannbettlaken.de DNS Report

Health Score: 66%

Need help fixing DNS ? Get an expert advise at support forum

Checked: 3 months before

Parent

NS records at parent servers

ns3.second-ns.de [ 193.47.99.4 ]
ns1.your-server.de [ 213.133.106.251 ]
ns.second-ns.com
[These were obtained from s.de.net.]

Glue at parent nameservers 0/7

WARNING The parent servers are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records. That may cause some extra milliseconds in DNS. This will usually occur if your DNS servers are not in the same TLD as your domain

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns1.your-server.de.	86400	IN	A	213.133.106.251) present at Parent, missing at (213.239.204.242)
(ns3.second-ns.de.	86400	IN	A	193.47.99.4) present at Parent, missing at (213.239.204.242)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns3.second-ns.de,ns.second-ns.com,ns1.your-server.de) at nameserver 213.239.204.242

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 0/10

Some nameservers does not respond:
2001:67c:192c::add:b3
2a01:4f8:d0a:2006::2

Nameserver name validity 7/7

SUCCESS All of the NS records that your nameservers report are valid (no IPs or partial domain names).

Number of nameservers 5/5

SUCCESS You have 3 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.

Lame nameservers 7/7

SUCCESS All the nameservers listed at the parent servers answer authoritatively for your domain.

Missing (stealth) nameservers 7/7

SUCCESS All your nameservers are also listed at the parent servers.

Root missing nameservers 7/7

SUCCESS All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.

Nameservers on separate class C's 7/7

SUCCESS Nameservers are in a different networks.

public IPs 7/7

SUCCESS All of your NS records appear to use public IPs.

SOA

SOA record

SOA record is:
Hostmaster email
postmaster.your-server.de
Serial
2017112201
Refresh
86400
Retry
10800
Expire
3600000
TTL
7200

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2017112201 That means that all your nameservers are using the same data.

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: ns1.your-server.de That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2017112201 This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. This number must be incremented every time you make a DNS change.

Refresh value 0/1

WARNING SOA Retry interval is : 86400 seconds. This seems too big;. (Values about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates.

Retry value 0/1

WARNING SOA Retry interval is : 10800 seconds. This seems too big;. (Values 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.

Expire value 0/1

WARNING SOA Expire time is : 3600000 seconds. This seems too big;. (Values 604800 to 2419200 seconds (1-4 weeks) is good). RFC1912 suggests 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.

TTL value 1/1

SUCCESS SOA Expire time is : 7200 seconds. This seems OK. (about 300 to 86400 seconds or 5 min - 24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.

Info

DNS trace

Trace to bettwaesche-spannbettlaken.de
lookup bettwaesche-spannbettlaken.de at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.de(194.0.0.53)
lookup bettwaesche-spannbettlaken.de at a.nic.de(194.0.0.53) 114 ms
a.nic.de(194.0.0.53) refer to ns1.your-server.de(213.133.106.251)
lookup bettwaesche-spannbettlaken.de at ns1.your-server.de(213.133.106.251) 91 ms
got A record 'bettwaesche-spannbettlaken.de IN A 88.198.195.29' from bettwaesche-spannbettlaken.de(213.133.106.251)
Total time: 215 ms