aealc.cu DNS Report

Health Score: 58%

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

Checked: 3 weeks before

Parent

NS records at parent servers 

ns1.etecsa.net
ns2.etecsa.net
ns3.etecsa.net
ns4.etecsa.net
ns5.etecsa.net
[These were obtained from cu.cctld.authdns.ripe.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 etecsa.net

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (ns3.etecsa.net.cu,ns1.etecsa.net,ns2.etecsa.net.cu,ns2.etecsa.net,ns4.etecsa.net,ns3.etecsa.net,ns5.etecsa.net,ns5.etecsa.net.cu,ns4.etecsa.net.cu,ns1.etecsa.net.cu) at nameserver 200.55.128.3
missing A record(s) for (ns2.etecsa.net,ns2.etecsa.net.cu,ns3.etecsa.net.cu,ns3.etecsa.net,ns4.etecsa.net,ns4.etecsa.net.cu,ns1.etecsa.net,ns5.etecsa.net,ns1.etecsa.net.cu,ns5.etecsa.net.cu) at nameserver 200.55.128.4
missing A record(s) for (ns2.etecsa.net.cu,ns3.etecsa.net.cu,ns3.etecsa.net,ns4.etecsa.net.cu,ns2.etecsa.net,ns5.etecsa.net.cu,ns1.etecsa.net,ns5.etecsa.net,ns4.etecsa.net,ns1.etecsa.net.cu) at nameserver 200.55.128.10
missing A record(s) for (ns5.etecsa.net,ns3.etecsa.net,ns3.etecsa.net.cu,ns1.etecsa.net.cu,ns1.etecsa.net,ns2.etecsa.net.cu,ns5.etecsa.net.cu,ns4.etecsa.net,ns4.etecsa.net.cu,ns2.etecsa.net) at nameserver 200.55.128.11

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (200.55.128.3 200.55.128.4 200.55.128.10 200.55.128.11) there are nameservers: ns3.etecsa.net.cu. ns1.etecsa.net. ns2.etecsa.net.cu. ns2.etecsa.net. ns4.etecsa.net. ns3.etecsa.net. ns5.etecsa.net. ns5.etecsa.net.cu. ns4.etecsa.net.cu. ns1.etecsa.net.cu.
At (181.225.231.195) there are nameservers:

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

Lame nameservers: 
181.225.231.195

Missing (stealth) nameservers 0/7

DANGER There are nameservers not listed at the parent servers: 
ns3.etecsa.net.cu.
ns2.etecsa.net.cu.
ns5.etecsa.net.cu.
ns4.etecsa.net.cu.
ns1.etecsa.net.cu.

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
admin.enet.cu
Serial
2017102700
Refresh
7200
Retry
1800
Expire
1209600
TTL
2000

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 2017102700 at nameserver(s) (200.55.128.3 200.55.128.4 200.55.128.11)
There is serial at nameserver(s) (181.225.231.195)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: ns1.etecsa.net That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2017102700 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 : 7200 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 : 1800 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 : 1209600 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 : 2000 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 aealc.cu
lookup aealc.cu at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns.ceniai.net.cu(169.158.128.136)
lookup aealc.cu at ns.ceniai.net.cu(169.158.128.136) 101 ms
ns.ceniai.net.cu(169.158.128.136) refer to ns4.etecsa.net(unknow IP)
extra IP lookup for ns4.etecsa.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns4.etecsa.net at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns4.etecsa.net at a.gtld-servers.net(192.5.6.30) 21 ms
a.gtld-servers.net(192.5.6.30) refer to ns1.etecsa.net(200.55.128.3)
lookup ns4.etecsa.net at ns1.etecsa.net(200.55.128.3) 103 ms
got A record 'ns4.etecsa.net IN A 200.55.128.11' from ns4.etecsa.net(200.55.128.3)
lookup aealc.cu at ns4.etecsa.net(200.55.128.11) 103 ms
RECORD does not exist
Total time: 348 ms