queerster.net DNS Report

Health Score: 86%

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

Checked: 2 months before

Parent

NS records at parent servers

nsa2.schlundtech.de
nsb2.schlundtech.de
nsc2.schlundtech.de
nsd2.schlundtech.de
[These were obtained from a.gtld-servers.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 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check schlundtech.de

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (nsa2.schlundtech.de,nsc2.schlundtech.de,nsd2.schlundtech.de,nsb2.schlundtech.de) at nameserver 62.116.159.12
missing A record(s) for (nsb2.schlundtech.de,nsa2.schlundtech.de,nsd2.schlundtech.de,nsc2.schlundtech.de) at nameserver 83.169.55.12
missing A record(s) for (nsd2.schlundtech.de,nsb2.schlundtech.de,nsc2.schlundtech.de,nsa2.schlundtech.de) at nameserver 89.146.248.22
missing A record(s) for (nsa2.schlundtech.de,nsb2.schlundtech.de,nsc2.schlundtech.de,nsd2.schlundtech.de) at nameserver 74.208.254.22

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 10/10

SUCCESS All of your nameservers listed at the parent nameservers responded.

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 4 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
post.steffen-bartels.de
Serial
2016121800
Refresh
43200
Retry
7200
Expire
1209600
TTL
600

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2016121800 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 queerster.net
lookup queerster.net at A.ROOT-SERVERS.NET(198.41.0.4) 22 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup queerster.net at a.gtld-servers.net(192.5.6.30) 81 ms
a.gtld-servers.net(192.5.6.30) refer to nsd2.schlundtech.de(unknow IP)
extra IP lookup for nsd2.schlundtech.de at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup nsd2.schlundtech.de at A.ROOT-SERVERS.NET(198.41.0.4) 24 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.de(194.0.0.53)
lookup nsd2.schlundtech.de at a.nic.de(194.0.0.53) 126 ms
a.nic.de(194.0.0.53) refer to any1.ns14.net(unknow IP)
extra IP lookup for any1.ns14.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup any1.ns14.net at A.ROOT-SERVERS.NET(198.41.0.4) 21 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup any1.ns14.net at e.gtld-servers.net(192.12.94.30) 23 ms
e.gtld-servers.net(192.12.94.30) refer to a.ns14.net(62.116.131.31)
lookup any1.ns14.net at a.ns14.net(62.116.131.31) 121 ms
got A record 'any1.ns14.net IN A 192.174.68.102' from any1.ns14.net(62.116.131.31)
lookup nsd2.schlundtech.de at any1.ns14.net(192.174.68.102) 11 ms
got A record 'nsd2.schlundtech.de IN A 74.208.254.22' from nsd2.schlundtech.de(192.174.68.102)
lookup queerster.net at nsd2.schlundtech.de(74.208.254.22) 40 ms
got A record 'queerster.net IN A 85.13.156.44' from queerster.net(74.208.254.22)
Total time: 469 ms