redlinetour.ru DNS Report

Health Score: 73%

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

Checked: 1 week before

Parent

NS records at parent servers

ns1.hc.ru
ns2.hc.ru
[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 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check hc.ru

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.hc.ru,ns2.hc.ru) at nameserver 89.111.177.252

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:
79.174.74.74

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 2/5

WARNING You have 2 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.hc.ru
Serial
2017080631
Refresh
3600
Retry
1800
Expire
604800
TTL
3600

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2017080631 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 : 3600 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 : 1800 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 : 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 redlinetour.ru
lookup redlinetour.ru at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup redlinetour.ru at a.dns.ripn.net(193.232.128.6) 60 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.hc.ru(unknow IP)
extra IP lookup for ns1.hc.ru at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.hc.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 ns1.hc.ru at a.dns.ripn.net(193.232.128.6) 62 ms
a.dns.ripn.net(193.232.128.6) refer to pdns1.infra.nic.ru(unknow IP)
extra IP lookup for pdns1.infra.nic.ru at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup pdns1.infra.nic.ru at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup pdns1.infra.nic.ru at a.dns.ripn.net(193.232.128.6) 56 ms
a.dns.ripn.net(193.232.128.6) refer to ns2-cloud.nic.ru(194.58.196.62)
lookup pdns1.infra.nic.ru at ns2-cloud.nic.ru(194.58.196.62) 4 ms
ns2-cloud.nic.ru(194.58.196.62) refer to pdns1.infra.nic.ru(31.177.84.133)
lookup pdns1.infra.nic.ru at pdns1.infra.nic.ru(31.177.84.133) 50 ms
got A record 'pdns1.infra.nic.ru IN A 31.177.84.133' from pdns1.infra.nic.ru(31.177.84.133)
lookup ns1.hc.ru at pdns1.infra.nic.ru(31.177.84.133) 50 ms
got A record 'ns1.hc.ru IN A 89.111.177.252' from ns1.hc.ru(31.177.84.133)
lookup redlinetour.ru at ns1.hc.ru(89.111.177.252) 53 ms
got A record 'redlinetour.ru IN A 92.53.96.114' from redlinetour.ru(89.111.177.252)
Total time: 349 ms