horecahome.ru DNS Report

Health Score: 77%

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

Checked: 7 months before

Parent

NS records at parent servers 

ns1.beget.com
ns1.beget.pro
ns2.beget.com
ns2.beget.pro
[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 beget.com Check beget.pro

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (ns1.beget.com,ns2.beget.com,ns1.beget.pro,ns2.beget.pro,ns1.beget.ru,ns2.beget.ru) at nameserver 5.101.159.11
missing A record(s) for (ns1.beget.com,ns2.beget.com,ns1.beget.pro,ns2.beget.pro,ns1.beget.ru,ns2.beget.ru) at nameserver 185.50.27.12

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

DANGER There are nameservers not listed at the parent servers: 
ns1.beget.ru.
ns2.beget.ru.

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
hostmaster.beget.com
Serial
1590910313
Refresh
300
Retry
600
Expire
86400
TTL
300

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 1590910313 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 0/1

WARNING SOA Retry interval is : 300 seconds. This seems too small. (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 : 600 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 : 86400 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 : 300 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 horecahome.ru
lookup horecahome.ru at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup horecahome.ru at a.dns.ripn.net(193.232.128.6) 116 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.beget.pro(unknow IP)
extra IP lookup for ns2.beget.pro at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.beget.pro at A.ROOT-SERVERS.NET(198.41.0.4) 2 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.pro.afilias-nst.info(199.182.0.1)
lookup ns2.beget.pro at a0.pro.afilias-nst.info(199.182.0.1) 34 ms
a0.pro.afilias-nst.info(199.182.0.1) refer to ns1.beget.pro(5.101.159.11)
lookup ns2.beget.pro at ns1.beget.pro(5.101.159.11) 113 ms
got A record 'ns2.beget.pro IN A 185.50.27.12' from ns2.beget.pro(5.101.159.11)
lookup horecahome.ru at ns2.beget.pro(185.50.27.12) 112 ms
got A record 'horecahome.ru IN A 87.236.16.132' from horecahome.ru(185.50.27.12)
Total time: 380 ms