intobservatory.ru DNS Report

Health Score: 86%

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

Checked: 1 week before

Parent

NS records at parent servers

dns.fastdns24.com
dns2.fastdns24.org
dns3.fastdns24.eu
dns4.fastdns24.link
[These were obtained from a.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 fastdns24.com Check fastdns24.org Check fastdns24.eu Check fastdns24.link

Nameservers A records 0/7

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

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

SUCCESS You have 4 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.fastvps.ru
Serial
2016080806
Refresh
10800
Retry
3600
Expire
604800
TTL
3600

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2016080806 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 intobservatory.ru
lookup intobservatory.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 intobservatory.ru at a.dns.ripn.net(193.232.128.6) 114 ms
a.dns.ripn.net(193.232.128.6) refer to dns4.fastdns24.link(unknow IP)
extra IP lookup for dns4.fastdns24.link at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns4.fastdns24.link at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns4.uniregistry.info(185.159.198.3)
lookup dns4.fastdns24.link at ns4.uniregistry.info(185.159.198.3) 8 ms
ns4.uniregistry.info(185.159.198.3) refer to pdns2.registrar-servers.com(unknow IP)
extra IP lookup for pdns2.registrar-servers.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup pdns2.registrar-servers.com at A.ROOT-SERVERS.NET(198.41.0.4) 38 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup pdns2.registrar-servers.com at a.gtld-servers.net(192.5.6.30) 37 ms
a.gtld-servers.net(192.5.6.30) refer to a1.verisigndns.com(209.112.113.33)
lookup pdns2.registrar-servers.com at a1.verisigndns.com(209.112.113.33) 10 ms
got A record 'pdns2.registrar-servers.com IN A 216.87.154.33' from pdns2.registrar-servers.com(209.112.113.33)
lookup dns4.fastdns24.link at pdns2.registrar-servers.com(216.87.154.33) 10 ms
got A record 'dns4.fastdns24.link IN A 95.216.25.5' from dns4.fastdns24.link(216.87.154.33)
lookup intobservatory.ru at dns4.fastdns24.link(95.216.25.5) 108 ms
got A record 'intobservatory.ru IN A 5.9.89.226' from intobservatory.ru(95.216.25.5)
Total time: 398 ms