arauco.cl DNS Report

Health Score: 76%

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

Checked: 2 months before

Parent

NS records at parent servers

ns1.arauco.cl [ 64.76.136.4 ]
ns2.arauco.cl [ 200.75.21.148 ]
ns3.arauco.cl [ 64.76.136.5 ]
ns4.arauco.cl [ 200.75.21.147 ]
ns5.arauco.cl [ 200.14.82.131 ]
[These were obtained from a.nic.cl.]

Glue at parent nameservers 7/7

SUCCESS Parent nameservers know A records for your domain, Very good !

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns.arauco.cl.		3600	IN	A	200.75.21.148) present at (64.76.136.4, 200.75.21.148, 64.76.136.5, 200.75.21.147, 200.14.82.131), missing at Parent
(ns.arauco.cl.		3600	IN	A	64.76.136.4) present at (64.76.136.4, 200.75.21.148, 64.76.136.5, 200.75.21.147, 200.14.82.131), missing at Parent
(ns.arauco.cl.		3600	IN	A	64.76.136.5) present at (64.76.136.4, 200.75.21.148, 64.76.136.5, 200.75.21.147, 200.14.82.131), missing at Parent
(ns.arauco.cl.		3600	IN	A	200.14.82.131) present at (64.76.136.4, 200.75.21.148, 64.76.136.5, 200.75.21.147, 200.14.82.131), missing at Parent
(ns.arauco.cl.		3600	IN	A	200.75.21.147) present at (64.76.136.4, 200.75.21.148, 64.76.136.5, 200.75.21.147, 200.14.82.131), missing at Parent

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

SUCCESS All the nameservers listed at the parent servers answer authoritatively for your domain.

Missing (stealth) nameservers 0/7

DANGER There are nameservers not listed at the parent servers:
ns.arauco.cl.

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
info.arauco.cl
Serial
2018091205
Refresh
1200
Retry
1200
Expire
1296000
TTL
3600

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 2018091205 at nameserver(s) (64.76.136.4 200.75.21.147)
There is serial 2018100501 at nameserver(s) (200.75.21.148 64.76.136.5 200.14.82.131)

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: ns.arauco.cl, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2018091205 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 : 1200 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 : 1200 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 : 1296000 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 arauco.cl
lookup arauco.cl at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.cl(190.124.27.10)
lookup arauco.cl at a.nic.cl(190.124.27.10) 125 ms
a.nic.cl(190.124.27.10) refer to ns1.arauco.cl(64.76.136.4)
lookup arauco.cl at ns1.arauco.cl(64.76.136.4) 130 ms
got A record 'arauco.cl IN A 144.217.39.254' from arauco.cl(64.76.136.4)
Total time: 266 ms