gruposexshop.cl DNS Report

Health Score: 71%

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

Checked: 1 month before

Parent

NS records at parent servers

ns1.gruposexshop.cl [ 192.185.106.56 ]
ns2.gruposexshop.cl [ 192.185.106.58 ]
[These were obtained from b.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.
(ns1.gruposexshop.cl.	3600	IN	A	192.185.106.56) present at Parent, missing at (192.185.106.56, 192.185.106.58)
(ns2.gruposexshop.cl.	3600	IN	A	192.185.106.58) present at Parent, missing at (192.185.106.56, 192.185.106.58)
(ns1057.websitewelcome.com.	14400	IN	A	192.185.106.56) present at (192.185.106.56, 192.185.106.58), missing at Parent
(ns1058.websitewelcome.com.	14400	IN	A	192.185.106.58) present at (192.185.106.56, 192.185.106.58), 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 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 0/7

DANGER There are nameservers not listed at the parent servers:
ns1057.websitewelcome.com.
ns1058.websitewelcome.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns1.gruposexshop.cl.
ns2.gruposexshop.cl.

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
root.volante.websitewelcome.com
Serial
2018072601
Refresh
86400
Retry
7200
Expire
3600000
TTL
86400

Serial agreement 7/7

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

SOA MNAME 0/3

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

Serial value 1/1

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

SUCCESS SOA Expire time is : 86400 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 gruposexshop.cl
lookup gruposexshop.cl at A.ROOT-SERVERS.NET(198.41.0.4) 33 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to b.nic.cl(200.7.4.7)
lookup gruposexshop.cl at b.nic.cl(200.7.4.7) 84 ms
b.nic.cl(200.7.4.7) refer to ns1.gruposexshop.cl(192.185.106.56)
lookup gruposexshop.cl at ns1.gruposexshop.cl(192.185.106.56) 60 ms
got A record 'gruposexshop.cl IN A 192.185.106.58' from gruposexshop.cl(192.185.106.56)
Total time: 177 ms