es DNS Report

Health Score: 65%

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

Checked: 4 months before

Parent

NS records at parent servers

g.nic.es [ 204.61.217.1 ]
ns-ext.nic.cl [ 200.1.123.14 ]
f.nic.es [ 130.206.1.7 ]
sns-pb.isc.org [ 192.5.4.1 ]
a.nic.es [ 194.69.254.1 ]
h.nic.es [ 194.0.33.53 ]
ns-es.nic.fr [ 194.0.9.1 ]
ns1.cesca.es
[These were obtained from a.root-servers.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 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(g.nic.es.		172800	IN	A	204.61.217.1) present at Parent, missing at (84.88.0.3)
(ns-ext.nic.cl.		172800	IN	A	200.1.123.14) present at Parent, missing at (84.88.0.3)
(f.nic.es.		172800	IN	A	130.206.1.7) present at Parent, missing at (84.88.0.3)
(sns-pb.isc.org.		172800	IN	A	192.5.4.1) present at Parent, missing at (84.88.0.3)
(a.nic.es.		172800	IN	A	194.69.254.1) present at Parent, missing at (84.88.0.3)
(h.nic.es.		172800	IN	A	194.0.33.53) present at Parent, missing at (84.88.0.3)
(ns-es.nic.fr.		172800	IN	A	194.0.9.1) present at Parent, missing at (84.88.0.3)
(ns1.cesca.es.		172800	IN	A	84.88.0.3) present at (84.88.0.3), missing at Parent

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (g.nic.es,ns-es.nic.fr,f.nic.es,sns-pb.isc.org,h.nic.es,a.nic.es,ns-ext.nic.cl) at nameserver 84.88.0.3

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 0/10

Some nameservers does not respond:
2001:500:14:7001:ad::1
2001:1398:1:0:200:1:123:14
2001:720:418:caf1::7
2001:500:2e::1
2001:67c:21cc:2000::64:41
2001:678:40::53
2001:678:c::1

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 8 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
hostmaster.nic.es
Serial
2019081405
Refresh
7200
Retry
7200
Expire
2592000
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2019081405 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: ns1.nic.es, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2019081405 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 : 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 : 2592000 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 es
lookup es at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.es(194.69.254.1)
lookup es at a.nic.es(194.69.254.1) 106 ms
RECORD does not exist
Total time: 143 ms