afraid.org DNS Report

Health Score: 72%

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

Checked: 2 years before

Parent

NS records at parent servers

namely.resolute-3.com
evergreen.v6.afraid.org
granite.afraid.org [ 70.39.97.245 ]
mint.ns37.net
ns7.afraid.org [ 69.197.18.173 ]
tungsten.afraid.org [ 173.193.220.116 ]
evergreen.afraid.org [ 50.23.197.93 ]
fueled.byhamsters.net
house.ofpenguins.net
[These were obtained from d0.org.afilias-nst.org.]

Glue at parent nameservers 0/7

WARNING The parent servers are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records. That may cause some extra milliseconds in DNS. This will usually occur if your DNS servers are not in the same TLD as your domain

NS

Mismatched glue 7/7

SUCCESS The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (house.ofpenguins.net,mint.ns37.net,fueled.byhamsters.net,namely.resolute-3.com,evergreen.v6.afraid.org) at nameserver 174.128.246.100
missing A record(s) for (house.ofpenguins.net,mint.ns37.net,fueled.byhamsters.net,namely.resolute-3.com,evergreen.v6.afraid.org) at nameserver 70.39.97.245
missing A record(s) for (evergreen.v6.afraid.org,house.ofpenguins.net,namely.resolute-3.com,mint.ns37.net,fueled.byhamsters.net) at nameserver 70.39.97.226
missing A record(s) for (fueled.byhamsters.net,house.ofpenguins.net,namely.resolute-3.com,mint.ns37.net,evergreen.v6.afraid.org) at nameserver 69.197.18.173
missing A record(s) for (evergreen.v6.afraid.org,house.ofpenguins.net,fueled.byhamsters.net,mint.ns37.net,namely.resolute-3.com) at nameserver 173.193.220.116
missing A record(s) for (mint.ns37.net,fueled.byhamsters.net,namely.resolute-3.com,house.ofpenguins.net,evergreen.v6.afraid.org) at nameserver 50.23.197.93
missing A record(s) for (namely.resolute-3.com,fueled.byhamsters.net,evergreen.v6.afraid.org,house.ofpenguins.net,mint.ns37.net) at nameserver 69.65.50.223
missing A record(s) for (mint.ns37.net,namely.resolute-3.com,evergreen.v6.afraid.org,fueled.byhamsters.net,house.ofpenguins.net) at nameserver 67.220.81.187

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:
2607:f0d0:1102:d5::2

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 9 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
dnsadmin.afraid.org
Serial
1701070033
Refresh
86400
Retry
7200
Expire
2419200
TTL
3600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 1701070033 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.afraid.org, but that server is not listed at the parent servers.

Serial value 1/1

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

WARNING SOA Retry interval is : 86400 seconds. This seems too big;. (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 : 7200 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 : 2419200 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 : 3600 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 afraid.org
lookup afraid.org at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d0.org.afilias-nst.org(199.19.57.1)
lookup afraid.org at d0.org.afilias-nst.org(199.19.57.1) 95 ms
d0.org.afilias-nst.org(199.19.57.1) refer to evergreen.afraid.org(50.23.197.93)
lookup afraid.org at evergreen.afraid.org(50.23.197.93) 45 ms
got A record 'afraid.org IN A 204.140.20.21' from afraid.org(50.23.197.93)
Total time: 151 ms