hispeetube.com DNS Report

Health Score: 72%

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

Checked: 1 week before

Parent

NS records at parent servers

ns3.above.com [ 69.43.160.19 69.43.160.22 ]
ns4.above.com [ 69.43.161.19 69.43.161.22 ]
[These were obtained from m.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.
(ns3.above.com.		172800	IN	A	69.43.160.19) present at Parent, missing at (69.43.160.22, 69.43.161.22)
(ns3.above.com.		172800	IN	A	69.43.160.22) present at Parent, missing at (69.43.160.22, 69.43.161.22)
(ns4.above.com.		172800	IN	A	69.43.161.19) present at Parent, missing at (69.43.160.22, 69.43.161.22)
(ns4.above.com.		172800	IN	A	69.43.161.22) present at Parent, missing at (69.43.160.22, 69.43.161.22)
(ns2.above.com.		3600	IN	A	69.43.161.19) present at (69.43.160.22, 69.43.161.22), missing at Parent
(ns1.above.com.		3600	IN	A	69.43.160.19) present at (69.43.160.22, 69.43.161.22), missing at Parent

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 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:
ns2.above.com.
ns1.above.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns3.above.com.
ns4.above.com.

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.trellian.com
Serial
2014071001
Refresh
10800
Retry
3600
Expire
604800
TTL
60

Serial agreement 7/7

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

SOA MNAME 0/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2014071001 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 : 10800 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 : 3600 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 0/1

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