elperro.tv DNS Report

Health Score: 82%

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

Checked: 1 week before

Parent

NS records at parent servers

ns1.bluecompany.cl
ns2.bluecompany.cl
[These were obtained from ac2.nstld.com.]

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 bluecompany.cl

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.bluecompany.cl,ns2.bluecompany.cl) at nameserver 52.21.190.41
missing A record(s) for (ns2.bluecompany.cl,ns1.bluecompany.cl) at nameserver 185.136.98.133

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

SOA record

SOA record is:
Hostmaster email
named.bluecompany.cl
Serial
2015101901
Refresh
10800
Retry
3600
Expire
3600000
TTL
300

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2015101901 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.bluecompany.cl That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2015101901 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 : 10800 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 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 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.

Info

DNS trace

Trace to elperro.tv
lookup elperro.tv at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ac1.nstld.com(192.42.173.30)
lookup elperro.tv at ac1.nstld.com(192.42.173.30) 2 ms
ac1.nstld.com(192.42.173.30) refer to ns1.bluecompany.cl(unknow IP)
extra IP lookup for ns1.bluecompany.cl at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.bluecompany.cl at A.ROOT-SERVERS.NET(198.41.0.4) 7 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.cl(200.1.121.10)
lookup ns1.bluecompany.cl at a.nic.cl(200.1.121.10) 151 ms
a.nic.cl(200.1.121.10) refer to ns-1798.awsdns-32.co.uk(unknow IP)
extra IP lookup for ns-1798.awsdns-32.co.uk at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns-1798.awsdns-32.co.uk at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to nsa.nic.uk(156.154.100.3)
lookup ns-1798.awsdns-32.co.uk at nsa.nic.uk(156.154.100.3) 7 ms
nsa.nic.uk(156.154.100.3) refer to g-ns-928.awsdns-32.co.uk(205.251.195.160)
lookup ns-1798.awsdns-32.co.uk at g-ns-928.awsdns-32.co.uk(205.251.195.160) 4 ms
got A record 'ns-1798.awsdns-32.co.uk IN A 205.251.199.6' from ns-1798.awsdns-32.co.uk(205.251.195.160)
lookup ns1.bluecompany.cl at ns-1798.awsdns-32.co.uk(205.251.199.6) 23 ms
got A record 'ns1.bluecompany.cl IN A 52.21.190.41' from ns1.bluecompany.cl(205.251.199.6)
lookup elperro.tv at ns1.bluecompany.cl(52.21.190.41) 9 ms
got A record 'elperro.tv IN A 52.21.1.214' from elperro.tv(52.21.190.41)
Total time: 212 ms