shukh.org.ua DNS Report

Health Score: 79%

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

Checked: 1 week before

Parent

NS records at parent servers

ns37.inhostedns.org
ns17.inhostedns.com
ns27.inhostedns.net
[These were obtained from ns.dn.ua.]

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 inhostedns.org Check inhostedns.com Check inhostedns.net

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns17.inhostedns.com,ns27.inhostedns.net,ns37.inhostedns.org) at nameserver 62.4.14.87
missing A record(s) for (ns17.inhostedns.com,ns27.inhostedns.net,ns37.inhostedns.org) at nameserver 185.104.44.23
missing A record(s) for (ns17.inhostedns.com,ns27.inhostedns.net,ns37.inhostedns.org) at nameserver 185.104.46.23

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
hostmaster.adm.tools
Serial
2016041333
Refresh
43200
Retry
7200
Expire
604800
TTL
900

Serial agreement 0/7

DANGER Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
There is serial 2016041333 at nameserver(s) (62.4.14.87)
There is serial 2016041311 at nameserver(s) (185.104.44.23)
There is serial 2016041316 at nameserver(s) (185.104.46.23)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: ns17.inhostedns.com That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2016041333 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 : 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 : 900 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 shukh.org.ua
lookup shukh.org.ua at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to cd1.ns.ua(194.0.1.9)
lookup shukh.org.ua at cd1.ns.ua(194.0.1.9) 110 ms
cd1.ns.ua(194.0.1.9) refer to ns.dn.ua(185.12.112.220)
lookup shukh.org.ua at ns.dn.ua(185.12.112.220) 52 ms
ns.dn.ua(185.12.112.220) refer to ns27.inhostedns.net(unknow IP)
extra IP lookup for ns27.inhostedns.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns27.inhostedns.net at A.ROOT-SERVERS.NET(198.41.0.4) 14 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns27.inhostedns.net at a.gtld-servers.net(192.5.6.30) 4 ms
a.gtld-servers.net(192.5.6.30) refer to ns21.inhostedns.net(185.104.46.20)
lookup ns27.inhostedns.net at ns21.inhostedns.net(185.104.46.20) 56 ms
got A record 'ns27.inhostedns.net IN A 185.104.46.23' from ns27.inhostedns.net(185.104.46.20)
lookup shukh.org.ua at ns27.inhostedns.net(185.104.46.23) 54 ms
got A record 'shukh.org.ua IN A 185.68.16.127' from shukh.org.ua(185.104.46.23)
Total time: 294 ms