himalaya-kanko.co.jp DNS Report

Health Score: 54%

Need help fixing DNS ? Get an expert advise at support forum

Checked: 1 month before

Parent

NS records at parent servers

ns4.xserver.jp
ns3.xserver.jp
ns5.xserver.jp
ns1.xserver.jp [ 219.94.200.166 219.94.200.167 219.94.200.168 219.94.200.169 219.94.200.170 219.94.200.246 219.94.200.70 219.94.200.71 219.94.200.164 219.94.200.165 ]
ns2.xserver.jp [ 210.188.201.61 210.188.201.246 157.112.182.221 157.112.182.222 157.112.182.223 157.112.182.224 157.112.182.225 ]
[These were obtained from a.dns.jp.]

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

SUCCESS The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.

Nameservers A records 7/7

SUCCESS 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 0/7

The NS records at your nameservers are different

Nameservers respond 0/10

Some nameservers does not respond:
183.90.224.228
219.94.200.247
157.112.182.217
219.94.200.165
157.112.182.225

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 5 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:
ns4.xserver.jp.
ns3.xserver.jp.
ns5.xserver.jp.
ns1.xserver.jp.
ns2.xserver.jp.

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
Serial
Refresh
Retry
Expire
TTL

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.

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: , but that server is not listed at the parent servers.

Serial value 0/1

WARNING SOA serial number is: 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 0/1

WARNING SOA Retry interval is : seconds. This seems too small. (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 0/1

WARNING SOA Retry interval is : seconds. This seems too small. (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 : seconds. This seems too small. (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 0/1

WARNING SOA Expire time is : 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.

Info

DNS trace

Trace to himalaya-kanko.co.jp
lookup himalaya-kanko.co.jp at A.ROOT-SERVERS.NET(198.41.0.4) 20 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.jp(203.119.1.1)
lookup himalaya-kanko.co.jp at a.dns.jp(203.119.1.1) 207 ms
a.dns.jp(203.119.1.1) refer to ns1.xserver.jp(219.94.200.166)
lookup himalaya-kanko.co.jp at ns1.xserver.jp(219.94.200.166) 208 ms
got A record 'himalaya-kanko.co.jp IN A 183.90.240.21' from himalaya-kanko.co.jp(219.94.200.166)
Total time: 435 ms