dnspod.net DNS Report

Health Score: 73%

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

Checked: 1 year before

Parent

NS records at parent servers

ns1.dnsv2.com [ 101.226.220.13 111.30.132.180 115.236.151.178 125.39.213.168 14.215.150.11 180.153.162.151 ]
ns2.dnsv2.com [ 111.30.132.180 122.225.217.193 180.153.10.167 180.163.19.11 182.140.167.167 183.60.57.177 220.249.242.11 ]
[These were obtained from e.gtld-servers.net.]

Glue at parent nameservers 7/7

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.dnsv2.com.		172800	IN	A	101.226.220.13) present at Parent, missing at (220.249.242.11)
(ns1.dnsv2.com.		172800	IN	A	111.30.132.180) present at Parent, missing at (220.249.242.11)
(ns1.dnsv2.com.		172800	IN	A	115.236.151.178) present at Parent, missing at (220.249.242.11)
(ns1.dnsv2.com.		172800	IN	A	125.39.213.168) present at Parent, missing at (220.249.242.11)
(ns1.dnsv2.com.		172800	IN	A	14.215.150.11) present at Parent, missing at (220.249.242.11)
(ns1.dnsv2.com.		172800	IN	A	180.153.162.151) present at Parent, missing at (220.249.242.11)
(ns2.dnsv2.com.		172800	IN	A	111.30.132.180) present at Parent, missing at (220.249.242.11)
(ns2.dnsv2.com.		172800	IN	A	122.225.217.193) present at Parent, missing at (220.249.242.11)
(ns2.dnsv2.com.		172800	IN	A	180.153.10.167) present at Parent, missing at (220.249.242.11)
(ns2.dnsv2.com.		172800	IN	A	180.163.19.11) present at Parent, missing at (220.249.242.11)
(ns2.dnsv2.com.		172800	IN	A	182.140.167.167) present at Parent, missing at (220.249.242.11)
(ns2.dnsv2.com.		172800	IN	A	183.60.57.177) present at Parent, missing at (220.249.242.11)
(ns2.dnsv2.com.		172800	IN	A	220.249.242.11) present at Parent, missing at (220.249.242.11)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.dnsv2.com,ns2.dnsv2.com) at nameserver 220.249.242.11

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 0/10

Some nameservers does not respond:
180.153.162.151

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
level3dnsadmin.dnspod.com
Serial
1483959239
Refresh
3600
Retry
180
Expire
1209600
TTL
600

Serial agreement 7/7

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

SOA MNAME 3/3

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

Serial value 1/1

SUCCESS SOA serial number is: 1483959239 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 : 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 1/1

SUCCESS SOA Expire time is : 1209600 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 : 600 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 dnspod.net
lookup dnspod.net at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup dnspod.net at a.gtld-servers.net(192.5.6.30) 12 ms
a.gtld-servers.net(192.5.6.30) refer to ns1.dnsv2.com(101.226.220.13)
lookup dnspod.net at ns1.dnsv2.com(101.226.220.13) 383 ms
got A record 'dnspod.net IN A 183.60.62.80' from dnspod.net(101.226.220.13)
Total time: 432 ms