Need help fixing DNS ? Get an expert advise at
support forum
Checked: 22 hours before
Parent
NS records at parent servers
ns2.22.cn
ns1.22.cn
[These were obtained from c.dns.cn.]
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 22.cn
Nameservers A records
0/7
Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.22.cn,ns2.22.cn) at nameserver 218.98.111.137
missing A record(s) for (ns1.22.cn,ns2.22.cn) at nameserver 218.98.111.136
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
dnsadmin.22.cn
Serial
1521977269
Refresh
28800
Retry
3600
Expire
1209600
TTL
600
Serial agreement
7/7
SUCCESS
All your nameservers agree that your SOA serial number is 1521977269 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.22.cn That server is listed at the parent servers, which is correct.
Serial value
1/1
SUCCESS
SOA serial number is: 1521977269 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 : 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 : 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
1/1
SUCCESS
SOA Expire time is : 1209600 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 kolangga.cn
lookup kolangga.cn at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to c.dns.cn(203.119.27.1)
lookup kolangga.cn at c.dns.cn(203.119.27.1) 121 ms
c.dns.cn(203.119.27.1) refer to ns1.22.cn(unknow IP)
extra IP lookup for ns1.22.cn at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.22.cn at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to c.dns.cn(203.119.27.1)
lookup ns1.22.cn at c.dns.cn(203.119.27.1) 126 ms
c.dns.cn(203.119.27.1) refer to ns1.22net.com(unknow IP)
extra IP lookup for ns1.22net.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.22net.com at A.ROOT-SERVERS.NET(198.41.0.4) 14 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns1.22net.com at a.gtld-servers.net(192.5.6.30) 11 ms
a.gtld-servers.net(192.5.6.30) refer to dns2.everdns.com(121.12.104.69)
lookup ns1.22net.com at dns2.everdns.com(121.12.104.69) 280 ms
got A record 'ns1.22net.com IN A 61.164.109.4' from ns1.22net.com(121.12.104.69)
lookup ns1.22.cn at ns1.22net.com(61.164.109.4) 327 ms
got A record 'ns1.22.cn IN A 218.66.171.136' from ns1.22.cn(61.164.109.4)
lookup kolangga.cn at ns1.22.cn(218.66.171.136) 325 ms
got A record 'kolangga.cn IN A 162.218.209.151' from kolangga.cn(218.66.171.136)