portaltyumen.ru DNS Report

Health Score: 59%

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

Checked: 6 days before

Parent

NS records at parent servers 

ns1.fastvps.ru [ 95.211.92.14 ]
ns2.fastvps.ru [ 178.132.200.26 ]
ns3.fastvps.ru [ 136.243.254.112 ]
[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.fastvps.ru.		345600	IN	A	95.211.92.14) present at Parent, missing at (136.243.254.112)
(ns2.fastvps.ru.		345600	IN	A	178.132.200.26) present at Parent, missing at (136.243.254.112)
(ns3.fastvps.ru.		345600	IN	A	136.243.254.112) present at Parent, missing at (136.243.254.112)

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (dns.fastdns24.com,dns2.fastdns24.org,dns3.fastdns24.eu,dns4.fastdns24.link) at nameserver 136.243.254.112

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: 
95.211.92.14
178.132.200.26

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

DANGER There are nameservers not listed at the parent servers: 
dns.fastdns24.com.
dns2.fastdns24.org.
dns3.fastdns24.eu.
dns4.fastdns24.link.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers: 
ns1.fastvps.ru.
ns2.fastvps.ru.
ns3.fastvps.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.fastvps.ru
Serial
2013042930
Refresh
10800
Retry
3600
Expire
604800
TTL
3600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2013042930 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: dns.fastdns24.com, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2013042930 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 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 portaltyumen.ru
lookup portaltyumen.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 portaltyumen.ru at a.dns.ripn.net(193.232.128.6) 53 ms
a.dns.ripn.net(193.232.128.6) refer to ns3.fastvps.ru(unknow IP)
extra IP lookup for ns3.fastvps.ru at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns3.fastvps.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 ns3.fastvps.ru at a.dns.ripn.net(193.232.128.6) 52 ms
a.dns.ripn.net(193.232.128.6) refer to dns.fastdns24.com(unknow IP)
extra IP lookup for dns.fastdns24.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns.fastdns24.com at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup dns.fastdns24.com at a.gtld-servers.net(192.5.6.30) 5 ms
a.gtld-servers.net(192.5.6.30) refer to ns17.domaincontrol.com(97.74.108.9)
lookup dns.fastdns24.com at ns17.domaincontrol.com(97.74.108.9) 8 ms
got A record 'dns.fastdns24.com IN A 176.31.3.154' from dns.fastdns24.com(97.74.108.9)
lookup ns3.fastvps.ru at dns.fastdns24.com(176.31.3.154) 11 ms
got A record 'ns3.fastvps.ru IN A 136.243.254.112' from ns3.fastvps.ru(176.31.3.154)
lookup portaltyumen.ru at ns3.fastvps.ru(136.243.254.112) 20 ms
got A record 'portaltyumen.ru IN A 185.4.72.221' from portaltyumen.ru(136.243.254.112)
Total time: 163 ms