autorivers.ru DNS Report

Health Score: 64%

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

Checked: 1 week before

Parent

NS records at parent servers

ns1.peterhost.ru [ 194.85.61.20 ]
ns2.peterhost.ru [ 194.226.96.8 ]
[These were obtained from a.dns.ripn.net.]

Glue at parent nameservers 7/7

SUCCESS Parent nameservers know A records for your domain, Very good !

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns1.peterhost.ru.	345600	IN	A	194.85.61.20) present at Parent, missing at (194.85.61.20, 194.226.96.8)
(ns2.peterhost.ru.	345600	IN	A	194.226.96.8) present at Parent, missing at (194.85.61.20, 194.226.96.8)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns4.nic.ru,ns3.nic.ru,ns8.nic.ru) at nameserver 194.85.61.20
missing A record(s) for (ns3.nic.ru,ns4.nic.ru,ns8.nic.ru) at nameserver 194.226.96.8

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

DANGER There are nameservers not listed at the parent servers:
ns4.nic.ru.
ns3.nic.ru.
ns8.nic.ru.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns1.peterhost.ru.
ns2.peterhost.ru.

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
16
Refresh
14400
Retry
3600
Expire
2592000
TTL
3600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 16 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: ns3.nic.ru, but that server is not listed at the parent servers.

Serial value 0/1

WARNING SOA serial number is: 16 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 autorivers.ru
lookup autorivers.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 autorivers.ru at a.dns.ripn.net(193.232.128.6) 48 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.peterhost.ru(unknow IP)
extra IP lookup for ns1.peterhost.ru at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.peterhost.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 ns1.peterhost.ru at a.dns.ripn.net(193.232.128.6) 53 ms
a.dns.ripn.net(193.232.128.6) refer to ns6.nic.RU(unknow IP)
extra IP lookup for ns6.nic.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns6.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 ns6.nic.RU at a.dns.ripn.net(193.232.128.6) 51 ms
a.dns.ripn.net(193.232.128.6) refer to ns2-cloud.nic.ru(194.58.196.62)
lookup ns6.nic.RU at ns2-cloud.nic.ru(194.58.196.62) 3 ms
got A record 'ns6.nic.RU IN A 31.177.74.100' from ns6.nic.RU(194.58.196.62)
lookup ns1.peterhost.ru at ns6.nic.RU(31.177.74.100) 52 ms
got A record 'ns1.peterhost.ru IN A 194.85.61.20' from ns1.peterhost.ru(31.177.74.100)
lookup autorivers.ru at ns1.peterhost.ru(194.85.61.20) 49 ms
got A record 'autorivers.ru IN A 91.189.114.18' from autorivers.ru(194.85.61.20)
Total time: 270 ms