feikz.net DNS Report

Health Score: 66%

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

Checked: 4 months before

Parent

NS records at parent servers

ns1.davs.for-ns.org
ns2.davs.for-ns.org
[These were obtained from e.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 davs.for-ns.org

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.example.com,ns2.example.com) at nameserver 94.130.219.239
missing A record(s) for (ns1.example.com,ns2.example.com) at nameserver 94.130.219.203

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 2/5

WARNING You have 2 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 0/7

DANGER There are nameservers not listed at the parent servers:
ns1.example.com.
ns2.example.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns1.davs.for-ns.org.
ns2.davs.for-ns.org.

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
root.example.com
Serial
2018010413
Refresh
3600
Retry
3600
Expire
604800
TTL
3600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2018010413 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: davs, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2018010413 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 : 3600 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 : 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 : 3600 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 feikz.net
lookup feikz.net at A.ROOT-SERVERS.NET(198.41.0.4) 12 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup feikz.net at a.gtld-servers.net(192.5.6.30) 9 ms
a.gtld-servers.net(192.5.6.30) refer to ns2.davs.for-ns.org(unknow IP)
extra IP lookup for ns2.davs.for-ns.org at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.davs.for-ns.org at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.org.afilias-nst.info(199.19.56.1)
lookup ns2.davs.for-ns.org at a0.org.afilias-nst.info(199.19.56.1) 163 ms
a0.org.afilias-nst.info(199.19.56.1) refer to for-ns.mars.orderbox-dns.com(unknow IP)
extra IP lookup for for-ns.mars.orderbox-dns.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup for-ns.mars.orderbox-dns.com 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 for-ns.mars.orderbox-dns.com at a.gtld-servers.net(192.5.6.30) 4 ms
a.gtld-servers.net(192.5.6.30) refer to andy.ns.cloudflare.com(173.245.59.101)
lookup for-ns.mars.orderbox-dns.com at andy.ns.cloudflare.com(173.245.59.101) 12 ms
got A record 'for-ns.mars.orderbox-dns.com IN A 162.251.82.124' from for-ns.mars.orderbox-dns.com(173.245.59.101)
lookup ns2.davs.for-ns.org at for-ns.mars.orderbox-dns.com(162.251.82.124) 46 ms
got A record 'ns2.davs.for-ns.org IN A 94.130.219.203' from ns2.davs.for-ns.org(162.251.82.124)
lookup feikz.net at ns2.davs.for-ns.org(94.130.219.203) 89 ms
got A record 'feikz.net IN A 94.130.219.239' from feikz.net(94.130.219.203)
Total time: 368 ms