xn--e1aaffjencflr.xn--p1ai DNS Report

Health Score: 90%

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

Checked: 3 weeks before

Parent

NS records at parent servers

ns1.jino.ru
ns2.jino.ru
[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 jino.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
hostmaster.jino.ru
Serial
2014041601
Refresh
16384
Retry
2048
Expire
1048576
TTL
86400

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2014041601 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 : 16384 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 : 2048 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 : 1048576 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 : 86400 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 xn--e1aaffjencflr.xn--p1ai
lookup xn--e1aaffjencflr.xn--p1ai at A.ROOT-SERVERS.NET(198.41.0.4) 41 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to f.dns.ripn.net(193.232.156.17)
lookup xn--e1aaffjencflr.xn--p1ai at f.dns.ripn.net(193.232.156.17) 2 ms
f.dns.ripn.net(193.232.156.17) refer to ns2.jino.ru(unknow IP)
extra IP lookup for ns2.jino.ru at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.jino.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 ns2.jino.ru at a.dns.ripn.net(193.232.128.6) 116 ms
a.dns.ripn.net(193.232.128.6) refer to ns4.jino.RU(unknow IP)
extra IP lookup for ns4.jino.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns4.jino.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 ns4.jino.RU at a.dns.ripn.net(193.232.128.6) 116 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.jino.RU(217.107.34.200)
lookup ns4.jino.RU at ns1.jino.RU(217.107.34.200) 125 ms
got A record 'ns4.jino.RU IN A 81.177.139.205' from ns4.jino.RU(217.107.34.200)
lookup ns2.jino.ru at ns4.jino.RU(81.177.139.205) 122 ms
got A record 'ns2.jino.ru IN A 217.107.217.16' from ns2.jino.ru(81.177.139.205)
lookup xn--e1aaffjencflr.xn--p1ai at ns2.jino.ru(217.107.217.16) 124 ms
got A record 'xn--e1aaffjencflr.xn--p1ai IN A 81.177.141.142' from xn--e1aaffjencflr.xn--p1ai(217.107.217.16)
Total time: 720 ms