2018guomo.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

f1g1ns1.dnspod.net [ 14.215.150.17 180.163.19.15 182.140.167.166 58.247.212.36 61.151.180.44 ]
f1g1ns2.dnspod.net [ 101.226.220.16 121.51.128.164 182.140.167.188 52.220.136.67 61.129.8.159 ]
[These were obtained from a.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.
(f1g1ns1.dnspod.net.	172800	IN	A	14.215.150.17) present at Parent, missing at (61.129.8.159)
(f1g1ns1.dnspod.net.	172800	IN	A	180.163.19.15) present at Parent, missing at (61.129.8.159)
(f1g1ns1.dnspod.net.	172800	IN	A	182.140.167.166) present at Parent, missing at (61.129.8.159)
(f1g1ns1.dnspod.net.	172800	IN	A	58.247.212.36) present at Parent, missing at (61.129.8.159)
(f1g1ns1.dnspod.net.	172800	IN	A	61.151.180.44) present at Parent, missing at (61.129.8.159)
(f1g1ns2.dnspod.net.	172800	IN	A	101.226.220.16) present at Parent, missing at (61.129.8.159)
(f1g1ns2.dnspod.net.	172800	IN	A	121.51.128.164) present at Parent, missing at (61.129.8.159)
(f1g1ns2.dnspod.net.	172800	IN	A	182.140.167.188) present at Parent, missing at (61.129.8.159)
(f1g1ns2.dnspod.net.	172800	IN	A	52.220.136.67) present at Parent, missing at (61.129.8.159)
(f1g1ns2.dnspod.net.	172800	IN	A	61.129.8.159) present at Parent, missing at (61.129.8.159)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (f1g1ns2.dnspod.net,f1g1ns1.dnspod.net) at nameserver 61.129.8.159

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:
61.151.180.44

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

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 1512475959 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: f1g1ns1.dnspod.net That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 1512475959 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 2018guomo.net
lookup 2018guomo.net at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup 2018guomo.net at e.gtld-servers.net(192.12.94.30) 40 ms
e.gtld-servers.net(192.12.94.30) refer to f1g1ns1.dnspod.net(14.215.150.17)
lookup 2018guomo.net at f1g1ns1.dnspod.net(14.215.150.17) 384 ms
got A record '2018guomo.net IN A 107.150.56.78' from 2018guomo.net(14.215.150.17)
Total time: 429 ms