[These were obtained from demand.alpha.aridns.net.au.]
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 worldnic.comCheck register.com
Nameservers A records
0/7
Some servers does not provide A records for nameservers.
missing A record(s) for (ns3.worldnic.com,ns4.worldnic.com) at nameserver 207.204.21.102
missing A record(s) for (ns3.worldnic.com,ns4.worldnic.com) at nameserver 207.204.40.102
Nameservers report identical NS records
0/7
The NS records at your nameservers are different
At (207.204.21.102 207.204.40.102) there are nameservers: ns3.worldnic.com. ns4.worldnic.com.
At (216.21.234.71 216.21.226.71) there are nameservers:
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 4 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
0/7
DANGER
There are nameservers not listed at your nameservers:
dns1.register.com.
dns2.register.com.
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
namehost.WORLDNIC.COM
Serial
114091116
Refresh
10800
Retry
3600
Expire
604800
TTL
7200
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.
There is serial 114091116 at nameserver(s) (207.204.21.102207.204.40.102)
There is serial at nameserver(s) (216.21.234.71216.21.226.71)
SOA MNAME
3/3
SUCCESS
SOA (Start of Authority) record states that your master (primary) name server is: NS3.WORLDNIC.COM That server is listed at the parent servers, which is correct.
Serial value
0/1
WARNING
SOA serial number is: 114091116 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 : 10800 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 : 604800 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 : 7200 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 zachraygroup.enterprises
lookup zachraygroup.enterprises at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to demand.alpha.aridns.net.au(37.209.192.7)
lookup zachraygroup.enterprises at demand.alpha.aridns.net.au(37.209.192.7) 3 ms
demand.alpha.aridns.net.au(37.209.192.7) refer to ns4.worldnic.com(unknow IP)
extra IP lookup for ns4.worldnic.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns4.worldnic.com at A.ROOT-SERVERS.NET(198.41.0.4) 7 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns4.worldnic.com at a.gtld-servers.net(192.5.6.30) 5 ms
a.gtld-servers.net(192.5.6.30) refer to heidi.ns.cloudflare.com(108.162.194.236)
lookup ns4.worldnic.com at heidi.ns.cloudflare.com(108.162.194.236) 19 ms
got A record 'ns4.worldnic.com IN A 207.204.21.102' from ns4.worldnic.com(108.162.194.236)
lookup zachraygroup.enterprises at ns4.worldnic.com(207.204.21.102) 96 ms
got A record 'zachraygroup.enterprises IN A 208.91.197.27' from zachraygroup.enterprises(207.204.21.102)