august.ru DNS Report

Health Score: 67%

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

Checked: 1 week before

Parent

NS records at parent servers 

ns3-l2.nic.ru
ns4-l2.nic.ru
ns8-l2.nic.ru
ns4-cloud.nic.ru [ 185.42.137.111 ]
ns8-cloud.nic.ru [ 194.58.196.62 ]
[These were obtained from b.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. 
(ns4-cloud.nic.ru.	345600	IN	A	185.42.137.111) present at Parent, missing at (193.232.146.1, 91.217.20.1, 91.217.21.1)
(ns8-cloud.nic.ru.	345600	IN	A	194.58.196.62) present at Parent, missing at (193.232.146.1, 91.217.20.1, 91.217.21.1)

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (ns8-l2.nic.ru,ns3-l2.nic.ru,ns4-l2.nic.ru,ns4-cloud.nic.ru,ns8-cloud.nic.ru) at nameserver 193.232.146.1
missing A record(s) for (ns8-l2.nic.ru,ns4-l2.nic.ru,ns8-cloud.nic.ru,ns3-l2.nic.ru,ns4-cloud.nic.ru) at nameserver 91.217.20.1
missing A record(s) for (ns8-l2.nic.ru,ns4-cloud.nic.ru,ns8-cloud.nic.ru,ns3-l2.nic.ru,ns4-l2.nic.ru) at nameserver 91.217.21.1

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: 
2a01:3f0:400::62
2a01:3f1:862::53

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
support.nic.ru
Serial
65012718
Refresh
14400
Retry
3600
Expire
2592000
TTL
3600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 65012718 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: ns3-l2.nic.ru That server is listed at the parent servers, which is correct.

Serial value 0/1

WARNING SOA serial number is: 65012718 This not 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 : 14400 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 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 august.ru
lookup august.ru at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup august.ru at a.dns.ripn.net(193.232.128.6) 56 ms
a.dns.ripn.net(193.232.128.6) refer to ns4-l2.nic.RU(unknow IP)
extra IP lookup for ns4-l2.nic.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns4-l2.nic.RU at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns4-l2.nic.RU at a.dns.ripn.net(193.232.128.6) 58 ms
a.dns.ripn.net(193.232.128.6) refer to ns1-cloud.nic.ru(185.42.137.111)
lookup ns4-l2.nic.RU at ns1-cloud.nic.ru(185.42.137.111) 31 ms
got A record 'ns4-l2.nic.RU IN A 91.217.20.1' from ns4-l2.nic.RU(185.42.137.111)
lookup august.ru at ns4-l2.nic.RU(91.217.20.1) 49 ms
got A record 'august.ru IN A 37.143.15.24' from august.ru(91.217.20.1)
Total time: 202 ms