kherson.ua DNS Report

Health Score: 66%

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

Checked: 1 week before

Parent

NS records at parent servers

ns.dn.ua [ 185.12.112.220 ]
nix.ns.ua [ 62.149.7.77 ]
ho1.ns.ks.ua [ 195.47.253.15 ]
ns.kharkov.ua
ns.ks-host.com
[These were obtained from cd1.ns.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 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(nix.ns.ua.		72072	IN	A	62.149.7.77) present at Parent, missing at (80.92.225.122, 193.109.128.221)
(ns.dn.ua.		72072	IN	A	185.12.112.220) present at Parent, missing at (193.109.128.221)
(ns.kharkov.ua.		3600	IN	A	80.92.225.122) present at (80.92.225.122), missing at Parent
(ns.ks-host.com.		3600	IN	A	193.109.128.221) present at (193.109.128.221), missing at Parent

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns.ks-host.com,nix.ns.ua) at nameserver 80.92.225.122
missing A record(s) for (ns.kharkov.ua,nix.ns.ua,ns.dn.ua) at nameserver 193.109.128.221

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 0/10

Some nameservers does not respond:
2a02:f080::220
2a03:6300:1:102::3
2001:67c:258::15

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 5 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.kherson.ua
Serial
2009059841
Refresh
28800
Retry
7200
Expire
2419200
TTL
86400

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2009059841 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 : 28800 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 : 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 : 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 kherson.ua
lookup kherson.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 kherson.ua at cd1.ns.ua(194.0.1.9) 4 ms
cd1.ns.ua(194.0.1.9) refer to ns.dn.ua(185.12.112.220)
lookup kherson.ua at ns.dn.ua(185.12.112.220) 143 ms
got A record 'kherson.ua IN A 31.28.161.196' from kherson.ua(185.12.112.220)
Total time: 151 ms