SUCCESS
Parent nameservers know A records for your domain, Very good !
NS
Mismatched glue
0/7
The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns1.dns.ne.jp. 86400 IN A 61.211.236.1) present at Parent, missing at (61.211.236.1, 133.167.21.1)
(ns2.dns.ne.jp. 86400 IN A 133.167.21.1) present at Parent, missing at (61.211.236.1, 133.167.21.1)
Nameservers A records
0/7
Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.dns.ne.jp,ns2.dns.ne.jp) at nameserver 61.211.236.1
missing A record(s) for (ns1.dns.ne.jp,ns2.dns.ne.jp) at nameserver 133.167.21.1
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
tech.sakura.ad.jp
Serial
2018030615
Refresh
3600
Retry
900
Expire
3600000
TTL
3600
Serial agreement
7/7
SUCCESS
All your nameservers agree that your SOA serial number is 2018030615 That means that all your nameservers are using the same data.
SOA MNAME
0/3
DANGER
SOA (Start of Authority) record states that your master (primary) name server is: master.dns.ne.jp, but that server is not listed at the parent servers.
Serial value
1/1
SUCCESS
SOA serial number is: 2018030615 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
1/1
SUCCESS
SOA Retry interval is : 3600 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 : 900 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
0/1
WARNING
SOA Expire time is : 3600000 seconds. This seems too big;. (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 log2.jp
lookup log2.jp at A.ROOT-SERVERS.NET(198.41.0.4) 6 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.jp(203.119.1.1)
lookup log2.jp at a.dns.jp(203.119.1.1) 238 ms
a.dns.jp(203.119.1.1) refer to ns1.dns.ne.jp(61.211.236.1)
lookup log2.jp at ns1.dns.ne.jp(61.211.236.1) 246 ms
got A record 'log2.jp IN A 153.127.81.150' from log2.jp(61.211.236.1)