[These were obtained from a0.org.afilias-nst.info.]
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
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
0/10
Some nameservers does not respond:
199.79.60.105
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
Serial
Refresh
Retry
Expire
TTL
Serial agreement
0/7
DANGER
Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
SOA MNAME
0/3
DANGER
SOA (Start of Authority) record states that your master (primary) name server is: , but that server is not listed at the parent servers.
Serial value
0/1
WARNING
SOA serial number is: 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
0/1
WARNING
SOA Retry interval is : seconds. This seems too small. (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
0/1
WARNING
SOA Retry interval is : seconds. This seems too small. (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 : seconds. This seems too small. (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
0/1
WARNING
SOA Expire time is : seconds. This seems too small. (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 hortibizindia.org
lookup hortibizindia.org at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.org.afilias-nst.info(199.19.56.1)
lookup hortibizindia.org at a0.org.afilias-nst.info(199.19.56.1) 3 ms
a0.org.afilias-nst.info(199.19.56.1) refer to sk.s5.cm.ns1.39.ztomy.com(unknow IP)
extra IP lookup for sk.s5.cm.ns1.39.ztomy.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup sk.s5.cm.ns1.39.ztomy.com at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup sk.s5.cm.ns1.39.ztomy.com at a.gtld-servers.net(192.5.6.30) 4 ms
a.gtld-servers.net(192.5.6.30) refer to usc5.akam.net(unknow IP)
extra IP lookup for usc5.akam.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup usc5.akam.net at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup usc5.akam.net at a.gtld-servers.net(192.5.6.30) 16 ms
a.gtld-servers.net(192.5.6.30) refer to a9-67.akam.net(184.85.248.67)
lookup usc5.akam.net at a9-67.akam.net(184.85.248.67) 16 ms
got A record 'usc5.akam.net IN A 96.7.50.65' from usc5.akam.net(184.85.248.67)
lookup sk.s5.cm.ns1.39.ztomy.com at usc5.akam.net(96.7.50.65) 239 ms
got A record 'sk.s5.cm.ns1.39.ztomy.com IN A 208.91.196.105' from sk.s5.cm.ns1.39.ztomy.com(96.7.50.65)
lookup hortibizindia.org at sk.s5.cm.ns1.39.ztomy.com(208.91.196.105) 114 ms
got A record 'hortibizindia.org IN A 208.91.196.105' from hortibizindia.org(208.91.196.105)