visitor-analytics.io DNS Report

Health Score: 86%

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

Checked: 6 months before

Parent

NS records at parent servers

ns1.first-ns.de
robotns2.second-ns.de
robotns3.second-ns.com
[These were obtained from b0.nic.io.]

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 first-ns.de Check second-ns.de Check second-ns.com

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.first-ns.de,robotns2.second-ns.de,robotns3.second-ns.com) at nameserver 213.239.242.238
missing A record(s) for (ns1.first-ns.de,robotns2.second-ns.de,robotns3.second-ns.com) at nameserver 213.133.105.6
missing A record(s) for (ns1.first-ns.de,robotns2.second-ns.de,robotns3.second-ns.com) at nameserver 193.47.99.3

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 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.robot.first-ns.de
Serial
2018041900
Refresh
14400
Retry
1800
Expire
604800
TTL
86400

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2018041900 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 : 14400 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 : 1800 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 : 604800 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 : 86400 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 visitor-analytics.io
lookup visitor-analytics.io at A.ROOT-SERVERS.NET(198.41.0.4) 21 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.nic.io(65.22.160.17)
lookup visitor-analytics.io at a0.nic.io(65.22.160.17) 85 ms
a0.nic.io(65.22.160.17) refer to robotns3.second-ns.com(unknow IP)
extra IP lookup for robotns3.second-ns.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup robotns3.second-ns.com at A.ROOT-SERVERS.NET(198.41.0.4) 38 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup robotns3.second-ns.com at a.gtld-servers.net(192.5.6.30) 18 ms
a.gtld-servers.net(192.5.6.30) refer to ns.second-ns.com(213.239.204.242)
lookup robotns3.second-ns.com at ns.second-ns.com(213.239.204.242) 142 ms
got A record 'robotns3.second-ns.com IN A 193.47.99.3' from robotns3.second-ns.com(213.239.204.242)
lookup visitor-analytics.io at robotns3.second-ns.com(193.47.99.3) 82 ms
got A record 'visitor-analytics.io IN A 136.243.146.200' from visitor-analytics.io(193.47.99.3)
Total time: 386 ms