mchost.ru DNS Report

Health Score: 72%

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

Checked: 1 year before

Parent

NS records at parent servers

nssec1.mchost.ru [ 178.208.73.126 ]
nssec2.mchost.ru [ 176.31.174.34 ]
nssec3.mchost.ru [ 146.185.178.209 ]
ns4-cloud.nic.ru [ 185.119.138.10 ]
ns8-cloud.nic.ru [ 185.119.136.12 ]
[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.
(ns4-cloud.nic.ru.	345600	IN	A	185.119.138.10) present at Parent, missing at (178.208.73.126, 176.31.174.34, 146.185.178.209)
(ns8-cloud.nic.ru.	345600	IN	A	185.119.136.12) present at Parent, missing at (178.208.73.126, 176.31.174.34, 146.185.178.209)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns4-cloud.nic.ru,ns8-cloud.nic.ru) at nameserver 178.208.73.126
missing A record(s) for (ns4-cloud.nic.ru,ns8-cloud.nic.ru) at nameserver 176.31.174.34
missing A record(s) for (ns4-cloud.nic.ru,ns8-cloud.nic.ru) at nameserver 146.185.178.209

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:5b0:9::a
2a01:5b0:8::c

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
info.mchost.ru
Serial
2212123141
Refresh
10800
Retry
3600
Expire
172800
TTL
600

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2212123141 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 : 10800 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 : 172800 seconds. This seems too small. (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 : 600 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 mchost.ru
lookup mchost.ru at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup mchost.ru at a.dns.ripn.net(193.232.128.6) 115 ms
a.dns.ripn.net(193.232.128.6) refer to nssec1.mchost.ru(178.208.73.126)
lookup mchost.ru at nssec1.mchost.ru(178.208.73.126) 77 ms
got A record 'mchost.ru IN A 185.203.72.169' from mchost.ru(178.208.73.126)
Total time: 229 ms