oltv.cz DNS Report

Health Score: 68%

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

Checked: 5 months before

Parent

NS records at parent servers

ns1.esmedia.eu
ns2.esmedia.eu
ns3.esmedia.eu
[These were obtained from a.ns.nic.cz.]

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 esmedia.eu

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns.gransy.com,ns2.gransy.com,ns3.gransy.com,ns4.gransy.com,ns5.gransy.com) at nameserver 77.78.104.149
missing A record(s) for (ns.gransy.com,ns2.gransy.com,ns3.gransy.com,ns4.gransy.com,ns5.gransy.com) at nameserver 217.16.185.221
missing A record(s) for (ns.gransy.com,ns2.gransy.com,ns3.gransy.com,ns4.gransy.com,ns5.gransy.com) at nameserver 77.78.126.35

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

DANGER There are nameservers not listed at the parent servers:
ns.gransy.com.
ns2.gransy.com.
ns3.gransy.com.
ns4.gransy.com.
ns5.gransy.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns1.esmedia.eu.
ns2.esmedia.eu.
ns3.esmedia.eu.

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.gransy.com
Serial
2017052929
Refresh
86400
Retry
900
Expire
1209600
TTL
1800

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2017052929 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 0/1

WARNING SOA Retry interval is : 86400 seconds. This seems too big;. (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 : 900 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 : 1209600 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 : 1800 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 oltv.cz
lookup oltv.cz at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.ns.nic.cz(194.0.12.1)
lookup oltv.cz at a.ns.nic.cz(194.0.12.1) 100 ms
a.ns.nic.cz(194.0.12.1) refer to ns3.esmedia.eu(unknow IP)
extra IP lookup for ns3.esmedia.eu at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns3.esmedia.eu at A.ROOT-SERVERS.NET(198.41.0.4) 12 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to cz.dns.eu(93.190.128.138)
lookup ns3.esmedia.eu at cz.dns.eu(93.190.128.138) 107 ms
cz.dns.eu(93.190.128.138) refer to ns3.esmedia.eu(77.78.126.35)
lookup ns3.esmedia.eu at ns3.esmedia.eu(77.78.126.35) 163 ms
got A record 'ns3.esmedia.eu IN A 77.78.126.35' from ns3.esmedia.eu(77.78.126.35)
lookup oltv.cz at ns3.esmedia.eu(77.78.126.35) 97 ms
got A record 'oltv.cz IN A 217.11.230.246' from oltv.cz(77.78.126.35)
Total time: 490 ms