gordon.edu DNS Report

Health Score: 76%

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

Checked: 10 months before

Parent

NS records at parent servers

ns1.dnsmadeeasy.com [ 208.80.124.2 ]
ns4.dnsmadeeasy.com [ 208.80.127.2 ]
ns3.dnsmadeeasy.com [ 208.80.125.2 ]
ns0.dnsmadeeasy.com [ 208.94.148.2 ]
ns2.dnsmadeeasy.com [ 208.80.126.2 ]
[These were obtained from a.edu-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.dnsmadeeasy.com.	172800	IN	A	208.80.124.2) present at Parent, missing at (208.80.124.2, 208.94.148.2, 208.80.126.2)
(ns4.dnsmadeeasy.com.	172800	IN	A	208.80.127.2) present at Parent, missing at (208.80.124.2, 208.94.148.2, 208.80.126.2)
(ns3.dnsmadeeasy.com.	172800	IN	A	208.80.125.2) present at Parent, missing at (208.80.124.2, 208.94.148.2, 208.80.126.2)
(ns0.dnsmadeeasy.com.	172800	IN	A	208.94.148.2) present at Parent, missing at (208.80.124.2, 208.94.148.2, 208.80.126.2)
(ns2.dnsmadeeasy.com.	172800	IN	A	208.80.126.2) present at Parent, missing at (208.80.124.2, 208.94.148.2, 208.80.126.2)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns0.dnsmadeeasy.com,ns1.dnsmadeeasy.com,ns3.dnsmadeeasy.com,ns4.dnsmadeeasy.com,ns2.dnsmadeeasy.com) at nameserver 208.80.124.2
missing A record(s) for (ns3.dnsmadeeasy.com,ns4.dnsmadeeasy.com,ns0.dnsmadeeasy.com,ns1.dnsmadeeasy.com,ns2.dnsmadeeasy.com) at nameserver 208.94.148.2
missing A record(s) for (ns1.dnsmadeeasy.com,ns4.dnsmadeeasy.com,ns3.dnsmadeeasy.com,ns0.dnsmadeeasy.com,ns2.dnsmadeeasy.com) at nameserver 208.80.126.2

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:
2600:1802:4::1
2600:1801:3::1

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 5 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
dns.dnsmadeeasy.com
Serial
2008010401
Refresh
28800
Retry
3600
Expire
604800
TTL
21600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2008010401 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: ns0.dnsmadeeasy.com That server is listed at the parent servers, which is correct.

Serial value 1/1

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

SUCCESS SOA Expire time is : 21600 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 gordon.edu
lookup gordon.edu at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to f.edu-servers.net(192.35.51.30)
lookup gordon.edu at f.edu-servers.net(192.35.51.30) 11 ms
f.edu-servers.net(192.35.51.30) refer to ns1.dnsmadeeasy.com(208.80.124.2)
lookup gordon.edu at ns1.dnsmadeeasy.com(208.80.124.2) 8 ms
got A record 'gordon.edu IN A 216.236.251.131' from gordon.edu(208.80.124.2)
Total time: 22 ms