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
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
The NS records at all your nameservers are identical.
All of your nameservers listed at the parent nameservers responded.
Nameserver name validity
All of the NS records that your nameservers report are valid (no IPs or partial domain names).
Number of nameservers
You have less then 2 nameservers, that may cause downtime
All the nameservers listed at the parent servers answer authoritatively for your domain.
Missing (stealth) nameservers
All your nameservers are also listed at the parent servers.
Root missing nameservers
There are nameservers not listed at your nameservers:
Nameservers on separate class C's
Nameservers are in a different networks.
All of your NS records appear to use public IPs.
SOA record is:
All your nameservers agree that your SOA serial number is 1594713547 That means that all your nameservers are using the same data.
SOA (Start of Authority) record states that your master (primary) name server is: 22.214.171.124, but that server is not listed at the parent servers.
SOA serial number is: 1594713547 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.
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.
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.
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.
SOA Expire time is : 60 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.
Trace to educatic.org.bo
lookup educatic.org.bo at A.ROOT-SERVERS.NET(126.96.36.199) 2 ms
A.ROOT-SERVERS.NET(188.8.131.52) refer to ns.dns.br(184.108.40.206)
lookup educatic.org.bo at ns.dns.br(220.127.116.11) 112 ms
ns.dns.br(18.104.22.168) refer to ns1.theconnectingcompany.com(unknow IP)
extra IP lookup for ns1.theconnectingcompany.com at root server A.ROOT-SERVERS.NET(22.214.171.124)
lookup ns1.theconnectingcompany.com at A.ROOT-SERVERS.NET(126.96.36.199) 2 ms
A.ROOT-SERVERS.NET(188.8.131.52) refer to a.gtld-servers.net(184.108.40.206)
lookup ns1.theconnectingcompany.com at a.gtld-servers.net(220.127.116.11) 45 ms
a.gtld-servers.net(18.104.22.168) refer to ns1.theconnectingcompany.com(22.214.171.124)
lookup ns1.theconnectingcompany.com at ns1.theconnectingcompany.com(126.96.36.199) 56 ms
got A record 'ns1.theconnectingcompany.com IN A 188.8.131.52' from ns1.theconnectingcompany.com(184.108.40.206)
lookup educatic.org.bo at ns1.theconnectingcompany.com(220.127.116.11) 52 ms
got A record 'educatic.org.bo IN A 18.104.22.168' from educatic.org.bo(22.214.171.124)