productosweb.org DNS Report

Health Score: 76%

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

Checked: 7 months before

Parent

NS records at parent servers

ns3.productosweb.org [ 72.29.96.11 ]
ns.productosweb.org [ 82.98.128.131 ]
ns2.productosweb.org [ 82.98.128.195 ]
ns4.productosweb.org [ 93.89.82.219 ]
[These were obtained from a0.org.afilias-nst.info.]

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.productosweb.org.	86400	IN	A	82.98.128.131) present at Parent, missing at (72.29.96.11, 82.98.128.131, 82.98.128.195, 93.89.82.219)
(ns2.productosweb.org.	86400	IN	A	82.98.128.195) present at Parent, missing at (72.29.96.11, 82.98.128.131, 82.98.128.195, 93.89.82.219)
(ns3.productosweb.org.	86400	IN	A	72.29.96.11) present at Parent, missing at (72.29.96.11, 82.98.128.131, 82.98.128.195, 93.89.82.219)
(ns4.productosweb.org.	86400	IN	A	93.89.82.219) present at Parent, missing at (72.29.96.11, 82.98.128.131, 82.98.128.195, 93.89.82.219)
(ns.gestiondecuenta.com.	300	IN	A	82.98.128.131) present at (72.29.96.11, 82.98.128.131, 82.98.128.195, 93.89.82.219), missing at Parent
(ns2.gestiondecuenta.com.	300	IN	A	82.98.128.195) present at (72.29.96.11, 82.98.128.131, 82.98.128.195, 93.89.82.219), missing at Parent
(ns3.gestiondecuenta.com.	300	IN	A	72.29.96.11) present at (72.29.96.11, 82.98.128.131, 82.98.128.195, 93.89.82.219), missing at Parent
(ns4.gestiondecuenta.com.	300	IN	A	93.89.82.219) present at (72.29.96.11, 82.98.128.131, 82.98.128.195, 93.89.82.219), 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 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 0/7

DANGER There are nameservers not listed at the parent servers:
ns3.gestiondecuenta.com.
ns2.gestiondecuenta.com.
ns4.gestiondecuenta.com.
ns.gestiondecuenta.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns3.productosweb.org.
ns.productosweb.org.
ns2.productosweb.org.
ns4.productosweb.org.

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
hostmaster.productosweb.org
Serial
2016031501
Refresh
3600
Retry
120
Expire
1209600
TTL
300

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2016031501 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: ns.dinahosting.com, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2016031501 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 : 3600 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 : 120 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 : 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 productosweb.org
lookup productosweb.org at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d0.org.afilias-nst.org(199.19.57.1)
lookup productosweb.org at d0.org.afilias-nst.org(199.19.57.1) 78 ms
d0.org.afilias-nst.org(199.19.57.1) refer to ns3.productosweb.org(72.29.96.11)
lookup productosweb.org at ns3.productosweb.org(72.29.96.11) 43 ms
got A record 'productosweb.org IN A 82.98.157.16' from productosweb.org(72.29.96.11)
Total time: 125 ms