atoo.su DNS Report

Health Score: 67%

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

Checked: 5 days before

Parent

NS records at parent servers

ns03.r01.ru
ns02.r01.ru
ns01.r01.ru
[These were obtained from d.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 r01.ru

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns3.nic.ru,ns4.nic.ru,ns8.nic.ru) at nameserver 193.232.130.110
missing A record(s) for (ns4.nic.ru,ns3.nic.ru,ns8.nic.ru) at nameserver 194.226.96.110
missing A record(s) for (ns8.nic.ru,ns3.nic.ru,ns4.nic.ru) at nameserver 109.70.27.110

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 3 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:
ns3.nic.ru.
ns4.nic.ru.
ns8.nic.ru.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns03.r01.ru.
ns02.r01.ru.
ns01.r01.ru.

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.nic.ru
Serial
10
Refresh
14400
Retry
3600
Expire
2592000
TTL
3600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 10 That means that all your nameservers are using the same data.

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: ns3.nic.ru, but that server is not listed at the parent servers.

Serial value 0/1

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

WARNING SOA Expire time is : 2592000 seconds. This seems too big;. (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 atoo.su
lookup atoo.su at A.ROOT-SERVERS.NET(198.41.0.4) 42 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d.dns.ripn.net(194.190.124.17)
lookup atoo.su at d.dns.ripn.net(194.190.124.17) 154 ms
d.dns.ripn.net(194.190.124.17) refer to ns01.r01.ru(unknow IP)
extra IP lookup for ns01.r01.ru at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns01.r01.ru at A.ROOT-SERVERS.NET(198.41.0.4) 41 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns01.r01.ru at a.dns.ripn.net(193.232.128.6) 116 ms
a.dns.ripn.net(193.232.128.6) refer to ns5.nic.ru(31.177.67.100)
lookup ns01.r01.ru at ns5.nic.ru(31.177.67.100) 121 ms
got A record 'ns01.r01.ru IN A 109.70.27.110' from ns01.r01.ru(31.177.67.100)
lookup atoo.su at ns01.r01.ru(109.70.27.110) 124 ms
got A record 'atoo.su IN A 31.177.94.58' from atoo.su(109.70.27.110)
Total time: 598 ms