YANDEX.RU DNS Report

Health Score: 77%

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

Checked: 4 months before

Parent

NS records at parent servers

ns9.z5h64q92x9.net
ns1.yandex.RU
ns2.yandex.RU
[These were obtained from a.dns.ripn.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 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns9.z5h64q92x9.net.	300	IN	A	80.239.201.9) present at (213.180.193.1, 93.158.134.1), missing at Parent

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns9.z5h64q92x9.net) at nameserver 80.239.201.9

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
sysadmin.yandex-team.ru
Serial
2019022715
Refresh
600
Retry
300
Expire
2592000
TTL
3600

Serial agreement 7/7

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

SOA MNAME 3/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2019022715 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 : 600 seconds. This seems too small. (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 : 300 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 0/1

WARNING SOA Expire time is : 2592000 seconds. This seems too big;. (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 YANDEX.RU
lookup YANDEX.RU at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup YANDEX.RU at a.dns.ripn.net(193.232.128.6) 117 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 117 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 117 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.yandex.RU(unknow IP)
extra IP lookup for ns1.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns1.yandex.RU at a.dns.ripn.net(193.232.128.6) 119 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.yandex.RU(unknow IP)
extra IP lookup for ns1.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns1.yandex.RU at a.dns.ripn.net(193.232.128.6) 118 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 118 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 119 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 124 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 126 ms
a.dns.ripn.net(193.232.128.6) refer to ns9.z5h64q92x9.net(unknow IP)
extra IP lookup for ns9.z5h64q92x9.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns9.z5h64q92x9.net at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns9.z5h64q92x9.net at e.gtld-servers.net(192.12.94.30) 9 ms
e.gtld-servers.net(192.12.94.30) refer to ns2.yandex.net(93.158.134.1)
lookup ns9.z5h64q92x9.net at ns2.yandex.net(93.158.134.1) 127 ms
got A record 'ns9.z5h64q92x9.net IN A 80.239.201.9' from ns9.z5h64q92x9.net(93.158.134.1)
lookup ns2.yandex.RU at ns9.z5h64q92x9.net(80.239.201.9) 134 ms
lookup ns2.yandex.RU at ns2.yandex.RU() 129 ms
lookup ns2.yandex.RU at ns2.yandex.RU() 132 ms
lookup ns2.yandex.RU at ns2.yandex.RU() 130 ms
lookup ns1.yandex.RU at ns2.yandex.RU() 132 ms
lookup ns1.yandex.RU at ns1.yandex.RU() 134 ms
lookup ns2.yandex.RU at ns1.yandex.RU() 134 ms
lookup ns2.yandex.RU at ns2.yandex.RU() 131 ms
lookup YANDEX.RU at ns2.yandex.RU() 135 ms
Total time: 2494 ms