happytailsmagazine.co.za DNS Report

Health Score: 83%

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

Checked: 4 months before

Parent

NS records at parent servers

ns2.cpns.co.za
ns4.cpns.co.za
ns1.cpns.co.za
ns3.cpns.co.za
[These were obtained from za1.dnsnode.net.]

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

Skip glue checking. Make sure the nameservers domain is good standing Check cpns.co.za

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns4.cpns.co.za,ns1.cpns.co.za,ns2.cpns.co.za,ns3.cpns.co.za) at nameserver 169.239.216.120
missing A record(s) for (ns1.cpns.co.za,ns3.cpns.co.za,ns2.cpns.co.za,ns4.cpns.co.za) at nameserver 164.132.100.141
missing A record(s) for (ns1.cpns.co.za,ns3.cpns.co.za,ns4.cpns.co.za,ns2.cpns.co.za) at nameserver 169.239.219.120
missing A record(s) for (ns4.cpns.co.za,ns3.cpns.co.za,ns1.cpns.co.za,ns2.cpns.co.za) at nameserver 149.56.97.89

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 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 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
jaco.sapetnel.co.za
Serial
2018051401
Refresh
86400
Retry
7200
Expire
3600000
TTL
120

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2018051401 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: ns1.cpns.co.za That server is listed at the parent servers, which is correct.

Serial value 1/1

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

WARNING SOA Expire time is : 3600000 seconds. This seems too big;. (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 : 120 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 happytailsmagazine.co.za
lookup happytailsmagazine.co.za at A.ROOT-SERVERS.NET(198.41.0.4) 13 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to za1.dnsnode.net(194.146.106.78)
lookup happytailsmagazine.co.za at za1.dnsnode.net(194.146.106.78) 23 ms
za1.dnsnode.net(194.146.106.78) refer to ns2.cpns.co.za(unknow IP)
extra IP lookup for ns2.cpns.co.za at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.cpns.co.za at A.ROOT-SERVERS.NET(198.41.0.4) 12 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to za1.dnsnode.net(194.146.106.78)
lookup ns2.cpns.co.za at za1.dnsnode.net(194.146.106.78) 11 ms
za1.dnsnode.net(194.146.106.78) refer to ns4.tld-ns.net(unknow IP)
extra IP lookup for ns4.tld-ns.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns4.tld-ns.net at A.ROOT-SERVERS.NET(198.41.0.4) 16 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns4.tld-ns.net at a.gtld-servers.net(192.5.6.30) 4 ms
a.gtld-servers.net(192.5.6.30) refer to ns1.tld-ns.com(169.239.219.115)
lookup ns4.tld-ns.net at ns1.tld-ns.com(169.239.219.115) 246 ms
got A record 'ns4.tld-ns.net IN A 164.132.104.47' from ns4.tld-ns.net(169.239.219.115)
lookup ns2.cpns.co.za at ns4.tld-ns.net(164.132.104.47) 105 ms
got A record 'ns2.cpns.co.za IN A 169.239.216.120' from ns2.cpns.co.za(164.132.104.47)
lookup happytailsmagazine.co.za at ns2.cpns.co.za(169.239.216.120) 245 ms
got A record 'happytailsmagazine.co.za IN A 41.222.34.149' from happytailsmagazine.co.za(169.239.216.120)
Total time: 675 ms