aleysk22.su DNS Report

Health Score: 89%

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

Checked: 1 week before

Parent

NS records at parent servers

ns1.pa.infobox.ru
ns2.pa.infobox.ru
[These were obtained from e.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 pa.infobox.ru

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

WARNING You have 2 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
aladmin.mail.ru
Serial
1074737
Refresh
14400
Retry
7200
Expire
2419200
TTL
3600

Serial agreement 7/7

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

Serial value 0/1

WARNING SOA serial number is: 1074737 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 : 14400 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 : 2419200 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 aleysk22.su
lookup aleysk22.su at A.ROOT-SERVERS.NET(198.41.0.4) 6 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d.dns.ripn.net(194.190.124.17)
lookup aleysk22.su at d.dns.ripn.net(194.190.124.17) 73 ms
d.dns.ripn.net(194.190.124.17) refer to ns1.pa.infobox.ru(unknow IP)
extra IP lookup for ns1.pa.infobox.ru at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.pa.infobox.ru at A.ROOT-SERVERS.NET(198.41.0.4) 7 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns1.pa.infobox.ru at a.dns.ripn.net(193.232.128.6) 129 ms
a.dns.ripn.net(193.232.128.6) refer to ns4.infobox.org(unknow IP)
extra IP lookup for ns4.infobox.org at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns4.infobox.org at A.ROOT-SERVERS.NET(198.41.0.4) 6 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d0.org.afilias-nst.org(199.19.57.1)
lookup ns4.infobox.org at d0.org.afilias-nst.org(199.19.57.1) 79 ms
d0.org.afilias-nst.org(199.19.57.1) refer to dns1.name-services.com(unknow IP)
extra IP lookup for dns1.name-services.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns1.name-services.com at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup dns1.name-services.com at a.gtld-servers.net(192.5.6.30) 3 ms
a.gtld-servers.net(192.5.6.30) refer to dns1.name-services.com(162.88.61.23)
lookup dns1.name-services.com at dns1.name-services.com(162.88.61.23) 9 ms
got A record 'dns1.name-services.com IN A 162.88.61.23' from dns1.name-services.com(162.88.61.23)
lookup ns4.infobox.org at dns1.name-services.com(162.88.61.23) 9 ms
got A record 'ns4.infobox.org IN A 77.221.128.198' from ns4.infobox.org(162.88.61.23)
lookup ns1.pa.infobox.ru at ns4.infobox.org(77.221.128.198) 110 ms
ns4.infobox.org(77.221.128.198) refer to ns2.pa.infobox.ru(77.221.128.146)
lookup ns1.pa.infobox.ru at ns2.pa.infobox.ru(77.221.128.146) 108 ms
got A record 'ns1.pa.infobox.ru IN A 77.221.140.41' from ns1.pa.infobox.ru(77.221.128.146)
lookup aleysk22.su at ns1.pa.infobox.ru(77.221.140.41) 112 ms
got A record 'aleysk22.su IN A 109.120.160.162' from aleysk22.su(77.221.140.41)
Total time: 659 ms