misoji-lady.net DNS Report

Health Score: 72%

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

Checked: 4 months before

Parent

NS records at parent servers

ns1.wordpress.com
ns2.wordpress.com
ns4.xserver.jp
ns3.wordpress.com
ns5.xserver.jp
[These were obtained from a.gtld-servers.net.]

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 wordpress.com Check xserver.jp

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
At (198.181.116.9 198.181.117.9 192.0.74.9) there are nameservers: ns1.wordpress.com. ns2.wordpress.com. ns3.wordpress.com.
At (183.90.224.226 157.112.182.218) there are nameservers: ns4.xserver.jp. ns2.xserver.jp. ns3.xserver.jp. ns1.xserver.jp. ns5.xserver.jp.

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

DANGER There are nameservers not listed at the parent servers:
ns2.xserver.jp.
ns3.xserver.jp.
ns1.xserver.jp.

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.wordpress.com
Serial
2005071858
Refresh
14400
Retry
7200
Expire
604800
TTL
86400

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 2005071858 at nameserver(s) (198.181.116.9 198.181.117.9 192.0.74.9)
There is serial 0 at nameserver(s) (183.90.224.226 157.112.182.218)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: ns1.wordpress.com That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2005071858 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 : 14400 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 : 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.

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 : 86400 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 misoji-lady.net
lookup misoji-lady.net at A.ROOT-SERVERS.NET(198.41.0.4) 41 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup misoji-lady.net at e.gtld-servers.net(192.12.94.30) 69 ms
e.gtld-servers.net(192.12.94.30) refer to ns5.xserver.jp(unknow IP)
extra IP lookup for ns5.xserver.jp at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns5.xserver.jp at A.ROOT-SERVERS.NET(198.41.0.4) 38 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.jp(203.119.1.1)
lookup ns5.xserver.jp at a.dns.jp(203.119.1.1) 165 ms
a.dns.jp(203.119.1.1) refer to ns3.xserver.jp(219.94.200.247)
lookup ns5.xserver.jp at ns3.xserver.jp(219.94.200.247) 162 ms
got A record 'ns5.xserver.jp IN A 210.188.201.247' from ns5.xserver.jp(219.94.200.247)
lookup misoji-lady.net at ns5.xserver.jp(210.188.201.247) 176 ms
got A record 'misoji-lady.net IN A 183.90.253.43' from misoji-lady.net(210.188.201.247)
Total time: 651 ms