jxdp.com.cn DNS Report

Health Score: 63%

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

Checked: 1 year before


NS records at parent servers

[These were obtained from a.dns.cn.]

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


Mismatched glue 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check ezdnscenter.com

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns3.cdncenter.com,ns5.cdncenter.com,ns1.cdncenter.com,ns4.cdncenter.com,ns2.cdncenter.com,ns6.cdncenter.com) at nameserver
missing A record(s) for (ns3.cdncenter.com,ns1.cdncenter.com,ns4.cdncenter.com,ns5.cdncenter.com,ns2.cdncenter.com,ns6.cdncenter.com) at nameserver

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

DANGER There are nameservers not listed at the parent servers:

Root missing nameservers 0/7

DANGER There are nameservers not listed 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 record

SOA record is:
Hostmaster email

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 66 That means that all your nameservers are using the same data.


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

Serial value 0/1

WARNING SOA serial number is: 66 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 : 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 : 180 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 : 2592000 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 : 7200 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.


DNS trace

Trace to jxdp.com.cn
lookup jxdp.com.cn at A.ROOT-SERVERS.NET( 40 ms
A.ROOT-SERVERS.NET( refer to c.dns.cn(
lookup jxdp.com.cn at c.dns.cn( 116 ms
c.dns.cn( refer to ns1.ezdnscenter.com(unknow IP)
extra IP lookup for ns1.ezdnscenter.com at root server A.ROOT-SERVERS.NET(
lookup ns1.ezdnscenter.com at A.ROOT-SERVERS.NET( 41 ms
A.ROOT-SERVERS.NET( refer to e.gtld-servers.net(
lookup ns1.ezdnscenter.com at e.gtld-servers.net( 23 ms
e.gtld-servers.net( refer to ins6.eznowdns.net(unknow IP)
extra IP lookup for ins6.eznowdns.net at root server A.ROOT-SERVERS.NET(
lookup ins6.eznowdns.net at A.ROOT-SERVERS.NET( 42 ms
A.ROOT-SERVERS.NET( refer to a.gtld-servers.net(
lookup ins6.eznowdns.net at a.gtld-servers.net( 43 ms
a.gtld-servers.net( refer to ins1.eznowdns.net(
lookup ins6.eznowdns.net at ins1.eznowdns.net( 220 ms
got A record 'ins6.eznowdns.net IN A' from ins6.eznowdns.net(
lookup ns1.ezdnscenter.com at ins6.eznowdns.net( 237 ms
got A record 'ns1.ezdnscenter.com IN A' from ns1.ezdnscenter.com(
lookup jxdp.com.cn at ns1.ezdnscenter.com( 226 ms
got A record 'jxdp.com.cn IN A' from jxdp.com.cn(
Total time: 988 ms