Parent nameservers know A records for your domain, Very good !
The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(mrtg.csu.edu.tw. 300 IN A 220.127.116.11) present at Parent, missing at (18.104.22.168)
(ibm220.csu.edu.tw. 300 IN A 22.214.171.124) present at Parent, missing at (126.96.36.199)
Nameservers A records
Some servers does not provide A records for nameservers.
missing A record(s) for (mrtg.csu.edu.tw) at nameserver 188.8.131.52
Nameservers report identical NS records
The NS records at your nameservers are different
At (184.108.40.206) there are nameservers: mrtg.csu.edu.tw. ibm220.csu.edu.tw.
At (220.127.116.11) there are nameservers: mrtg.csu.edu.tw.
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 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
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
All of the nameservers listed at the parent nameservers are also listed as NS records 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:
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 2019041901 at nameserver(s) (18.104.22.168)
There is serial 763 at nameserver(s) (22.214.171.124)
SOA (Start of Authority) record states that your master (primary) name server is: ibm220.csu.edu.tw That server is listed at the parent servers, which is correct.
SOA serial number is: 2019041901 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 : 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.
SOA Retry interval is : 7200 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 : 259200 seconds. This seems too big;. (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 csu.edu.tw
lookup csu.edu.tw at A.ROOT-SERVERS.NET(126.96.36.199) 46 ms
A.ROOT-SERVERS.NET(188.8.131.52) refer to g.dns.tw(184.108.40.206)
lookup csu.edu.tw at g.dns.tw(220.127.116.11) 207 ms
g.dns.tw(18.104.22.168) refer to moemoon.edu.tw(22.214.171.124)
lookup csu.edu.tw at moemoon.edu.tw(126.96.36.199) 203 ms
moemoon.edu.tw(188.8.131.52) refer to ibm220.csu.edu.tw(184.108.40.206)
lookup csu.edu.tw at ibm220.csu.edu.tw(220.127.116.11) 216 ms
RECORD does not exist