droni.me DNS Report

Health Score: 76%

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

Checked: 1 month before

Parent

NS records at parent servers

ns2.1984.is
ns1.1984.is
dns1.computel2.com
ns0.1984.is
[These were obtained from c0.nic.me.]

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 1984.is Check computel2.com

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (dns1.computel2.com) at nameserver 93.95.226.52
missing A record(s) for (dns1.computel2.com) at nameserver 45.76.136.88
missing A record(s) for (ns1.1984.is,ns0.1984.is) at nameserver 149.13.146.55
missing A record(s) for (dns1.computel2.com) at nameserver 185.112.145.12

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 0/7

DANGER There are nameservers not listed at your nameservers:
ns2.1984.is.

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
master.computel2.com
Serial
2018101600
Refresh
7200
Retry
3600
Expire
2419200
TTL
7200

Serial agreement 7/7

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

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: dns1.droni.me, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2018101600 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 : 7200 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 : 3600 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 : 2419200 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 : 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 droni.me
lookup droni.me at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.nic.me(199.253.59.1)
lookup droni.me at a0.nic.me(199.253.59.1) 158 ms
a0.nic.me(199.253.59.1) refer to ns0.1984.is(unknow IP)
extra IP lookup for ns0.1984.is at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns0.1984.is at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to isgate.is(193.4.58.51)
lookup ns0.1984.is at isgate.is(193.4.58.51) 86 ms
isgate.is(193.4.58.51) refer to ns1.1984.is(45.76.136.88)
lookup ns0.1984.is at ns1.1984.is(45.76.136.88) 73 ms
got A record 'ns0.1984.is IN A 185.112.145.12' from ns0.1984.is(45.76.136.88)
lookup droni.me at ns0.1984.is(185.112.145.12) 131 ms
got A record 'droni.me IN A 149.13.146.56' from droni.me(185.112.145.12)
Total time: 469 ms