haddonfortnightly.org DNS Report

Health Score: 80%

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

Checked: 4 months before


NS records at parent servers

[These were obtained from a0.org.afilias-nst.info.]

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


Mismatched glue 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check s5.bns2.ns129.searchreinvented.com Check s5.bns1.ns129.searchreinvented.com

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

Some nameservers does not respond:

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 record

SOA record is:
Hostmaster email

Serial agreement 7/7

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


SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: sk.s5.bns1.ns129.searchreinvented.com That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2011062801 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 : 900 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 : 300 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.


DNS trace

Trace to haddonfortnightly.org
lookup haddonfortnightly.org at A.ROOT-SERVERS.NET( 41 ms
A.ROOT-SERVERS.NET( refer to a0.org.afilias-nst.info(
lookup haddonfortnightly.org at a0.org.afilias-nst.info( 153 ms
a0.org.afilias-nst.info( refer to sk.s5.bns1.ns129.searchreinvented.com(unknow IP)
extra IP lookup for sk.s5.bns1.ns129.searchreinvented.com at root server A.ROOT-SERVERS.NET(
lookup sk.s5.bns1.ns129.searchreinvented.com at A.ROOT-SERVERS.NET( 42 ms
A.ROOT-SERVERS.NET( refer to e.gtld-servers.net(
lookup sk.s5.bns1.ns129.searchreinvented.com at e.gtld-servers.net( 24 ms
e.gtld-servers.net( refer to usc5.akam.net(unknow IP)
extra IP lookup for usc5.akam.net at root server A.ROOT-SERVERS.NET(
lookup usc5.akam.net at A.ROOT-SERVERS.NET( 41 ms
A.ROOT-SERVERS.NET( refer to a.gtld-servers.net(
lookup usc5.akam.net at a.gtld-servers.net( 41 ms
a.gtld-servers.net( refer to a9-67.akam.net(
lookup usc5.akam.net at a9-67.akam.net( 97 ms
got A record 'usc5.akam.net IN A' from usc5.akam.net(
lookup sk.s5.bns1.ns129.searchreinvented.com at usc5.akam.net( 64 ms
got A record 'sk.s5.bns1.ns129.searchreinvented.com IN A' from sk.s5.bns1.ns129.searchreinvented.com(
lookup haddonfortnightly.org at sk.s5.bns1.ns129.searchreinvented.com( 39 ms
got A record 'haddonfortnightly.org IN A' from haddonfortnightly.org(
Total time: 542 ms