shifter.ru DNS Report

Health Score: 85%

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

Checked: 1 month before

Parent

NS records at parent servers 

ns1.timeweb.ru [ 92.53.116.200 ]
ns2.timeweb.ru [ 92.53.98.100 ]
ns3.timeweb.org
ns4.timeweb.org
[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 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers. 
(ns1.timeweb.ru.		345600	IN	A	92.53.116.200) present at Parent, missing at (92.53.116.200, 92.53.98.100, 92.53.98.42)
(ns3.timeweb.org.		600	IN	A	92.53.116.200) present at (92.53.116.200, 92.53.98.100, 92.53.98.42), missing at Parent
(ns4.timeweb.org.		600	IN	A	92.53.98.42) present at (92.53.116.200, 92.53.98.100, 92.53.98.42), missing at Parent
(ns1.timeweb.ru.		600	IN	A	92.53.116.26) present at (92.53.116.200, 92.53.98.100, 92.53.98.42), missing at Parent

Nameservers A records 7/7

SUCCESS Nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.

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
dns.timeweb.ru
Serial
31082024
Refresh
28800
Retry
7200
Expire
604800
TTL
600

Serial agreement 7/7

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

Serial value 0/1

WARNING SOA serial number is: 31082024 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 : 28800 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 : 7200 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 : 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 shifter.ru
lookup shifter.ru at A.ROOT-SERVERS.NET(198.41.0.4) 72 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup shifter.ru at a.dns.ripn.net(193.232.128.6) 118 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.timeweb.RU(unknow IP)
extra IP lookup for ns2.timeweb.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.timeweb.RU at A.ROOT-SERVERS.NET(198.41.0.4) 63 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.timeweb.RU at a.dns.ripn.net(193.232.128.6) 125 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.timeweb.RU(92.53.116.200)
lookup ns2.timeweb.RU at ns1.timeweb.RU(92.53.116.200) 107 ms
got A record 'ns2.timeweb.RU IN A 92.53.98.100' from ns2.timeweb.RU(92.53.116.200)
lookup shifter.ru at ns2.timeweb.RU(92.53.98.100) 107 ms
got A record 'shifter.ru IN A 95.213.195.173' from shifter.ru(92.53.98.100)
Total time: 592 ms