therainforestconservancy.com DNS Report

Health Score: 57%

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

Checked: 7 months before

Parent

NS records at parent servers

dns1.register.com [ 216.21.234.71 ]
dns2.register.com [ 216.21.226.71 ]
ns65.worldnic.com [ 207.204.40.133 ]
ns66.worldnic.com [ 207.204.21.133 ]
[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.
(dns1.register.com.	172800	IN	A	216.21.234.71) present at Parent, missing at (216.21.234.71, 216.21.226.71, 207.204.40.133, 207.204.21.133)
(dns2.register.com.	172800	IN	A	216.21.226.71) present at Parent, missing at (216.21.234.71, 216.21.226.71, 207.204.40.133, 207.204.21.133)
(ns65.worldnic.com.	172800	IN	A	207.204.40.133) present at Parent, missing at (216.21.234.71, 216.21.226.71, 207.204.40.133, 207.204.21.133)
(ns66.worldnic.com.	172800	IN	A	207.204.21.133) present at Parent, missing at (216.21.234.71, 216.21.226.71, 207.204.40.133, 207.204.21.133)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns65.worldnic.com,ns66.worldnic.com) at nameserver 207.204.40.133
missing A record(s) for (ns66.worldnic.com,ns65.worldnic.com) at nameserver 207.204.21.133

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (216.21.234.71 216.21.226.71) there are nameservers:
At (207.204.40.133 207.204.21.133) there are nameservers: ns65.worldnic.com. ns66.worldnic.com.

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

DANGER There are nameservers not listed at your nameservers:
dns1.register.com.
dns2.register.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
Serial
Refresh
Retry
Expire
TTL

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 at nameserver(s) (216.21.234.71 216.21.226.71)
There is serial 118051612 at nameserver(s) (207.204.40.133 207.204.21.133)

SOA MNAME 0/3

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

Serial value 0/1

WARNING SOA serial number is: 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 : seconds. This seems too small. (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 0/1

WARNING SOA Retry interval is : seconds. This seems too small. (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 : seconds. This seems too small. (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 : 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.

Info

DNS trace

Trace to therainforestconservancy.com
lookup therainforestconservancy.com at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup therainforestconservancy.com at a.gtld-servers.net(192.5.6.30) 20 ms
a.gtld-servers.net(192.5.6.30) refer to dns1.register.com(216.21.234.71)
lookup therainforestconservancy.com at dns1.register.com(216.21.234.71) 34 ms
got A record 'therainforestconservancy.com IN A 141.8.225.68' from therainforestconservancy.com(216.21.234.71)
Total time: 64 ms