ishelminger.de DNS Report

Health Score: 69%

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

Checked: 6 days before

Parent

NS records at parent servers

ns2.hans.hosteurope.de
multins04.dnsbox.de [ 74.208.254.4 ]
multins02.dnsbox.de [ 217.160.113.37 83.169.55.4 ]
multins01.dnsbox.de [ 62.116.159.4 ]
multins03.dnsbox.de [ 89.146.248.4 ]
[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.
(multins01.dnsbox.de.	86400	IN	A	62.116.159.4) present at Parent, missing at (80.237.128.10)
(multins02.dnsbox.de.	86400	IN	A	217.160.113.37) present at Parent, missing at (80.237.128.10)
(multins02.dnsbox.de.	86400	IN	A	83.169.55.4) present at Parent, missing at (80.237.128.10)
(multins03.dnsbox.de.	86400	IN	A	89.146.248.4) present at Parent, missing at (80.237.128.10)
(multins04.dnsbox.de.	86400	IN	A	74.208.254.4) present at Parent, missing at (80.237.128.10)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns2.hans.hosteurope.de,multins01.dnsbox.de,multins02.dnsbox.de,multins03.dnsbox.de,multins04.dnsbox.de) at nameserver 80.237.128.10

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:
2607:f1c0:849:fe00:74:208:254:4
2001:8d8:580:401:217:160:113:37
2001:4178:3:a357:62:116:159:4
2a01:130:2000:118:89:146:248:4

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 5 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
domains.issociate.de
Serial
2017112000
Refresh
43200
Retry
7200
Expire
1209600
TTL
600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2017112000 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: multins01.dnsbox.de That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2017112000 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 1/1

SUCCESS SOA Retry interval is : 43200 seconds. This seems OK. (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 1/1

SUCCESS SOA Retry interval is : 7200 seconds. This seems OK. (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 1/1

SUCCESS SOA Expire time is : 1209600 seconds. This seems OK. (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 : 600 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 ishelminger.de
lookup ishelminger.de at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.de(194.0.0.53)
lookup ishelminger.de at a.nic.de(194.0.0.53) 128 ms
a.nic.de(194.0.0.53) refer to multins02.dnsbox.de(83.169.55.4)
lookup ishelminger.de at multins02.dnsbox.de(83.169.55.4) 92 ms
got A record 'ishelminger.de IN A 195.63.103.148' from ishelminger.de(83.169.55.4)
Total time: 225 ms