Need help fixing DNS ? Get an expert advise at
support forum
Checked: 5 months before
Parent
NS records at parent servers
admns2.hinet.net
admns1.hinet.net
[These were obtained from g.twnic.net.tw.]
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 hinet.net
Nameservers A records
0/7
Some servers does not provide A records for nameservers.
missing A record(s) for (admns2.hinet.net,admns1.hinet.net) at nameserver 203.74.116.192
missing A record(s) for (admns2.hinet.net,admns1.hinet.net) at nameserver 168.95.192.11
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
hostmaster.hinet.net
Serial
2019032204
Refresh
86400
Retry
1800
Expire
604800
TTL
3600
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 2019032204 at nameserver(s) (203.74.116.192)
There is serial 2019032206 at nameserver(s) (168.95.192.11)
SOA MNAME
3/3
SUCCESS
SOA (Start of Authority) record states that your master (primary) name server is: admns1.hinet.net That server is listed at the parent servers, which is correct.
Serial value
1/1
SUCCESS
SOA serial number is: 2019032204 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
0/1
WARNING
SOA Retry interval is : 86400 seconds. This seems too big;. (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 : 1800 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 : 3600 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 ctspl.com.tw
lookup ctspl.com.tw at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to g.dns.tw(220.229.225.195)
lookup ctspl.com.tw at g.dns.tw(220.229.225.195) 211 ms
g.dns.tw(220.229.225.195) refer to b.twnic.net.tw(203.73.24.24)
lookup ctspl.com.tw at b.twnic.net.tw(203.73.24.24) 204 ms
b.twnic.net.tw(203.73.24.24) refer to admns1.hinet.net(unknow IP)
extra IP lookup for admns1.hinet.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup admns1.hinet.net at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup admns1.hinet.net at a.gtld-servers.net(192.5.6.30) 20 ms
a.gtld-servers.net(192.5.6.30) refer to ans1.hinet.net(168.95.192.15)
lookup admns1.hinet.net at ans1.hinet.net(168.95.192.15) 197 ms
got A record 'admns1.hinet.net IN A 168.95.192.11' from admns1.hinet.net(168.95.192.15)
lookup ctspl.com.tw at admns1.hinet.net(168.95.192.11) 197 ms
got A record 'ctspl.com.tw IN A 60.249.6.190' from ctspl.com.tw(168.95.192.11)