delsol.COM.PY DNS Report

Health Score: 65%

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

Checked: 3 days before

Parent

NS records at parent servers

ns2.teixido.co
ns4.teixido.co
n3.teixido.co
ns1.teixido.co
[These were obtained from p.dns.py.]

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 teixido.co

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

Some nameservers does not respond:
45.56.113.84

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:
ns1.linode.com.
ns4.linode.com.
ns5.linode.com.
ns2.linode.com.
ns3.linode.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns2.teixido.co.
ns4.teixido.co.
n3.teixido.co.
ns1.teixido.co.

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
lars.teixido.co
Serial
2016022773
Refresh
14400
Retry
14400
Expire
1209600
TTL
86400

Serial agreement 7/7

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

Serial value 1/1

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

WARNING SOA Retry interval is : 14400 seconds. This seems too big;. (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 : 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 delsol.com.py
lookup delsol.com.py at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to b.dns.py(200.160.0.5)
lookup delsol.com.py at b.dns.py(200.160.0.5) 156 ms
b.dns.py(200.160.0.5) refer to ns2.teixido.co(unknow IP)
extra IP lookup for ns2.teixido.co at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.teixido.co at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns1.cctld.co(156.154.100.25)
lookup ns2.teixido.co at ns1.cctld.co(156.154.100.25) 4 ms
ns1.cctld.co(156.154.100.25) refer to NS1.LINODE.COM(unknow IP)
extra IP lookup for NS1.LINODE.COM at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup NS1.LINODE.COM at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup NS1.LINODE.COM at a.gtld-servers.net(192.5.6.30) 4 ms
a.gtld-servers.net(192.5.6.30) refer to NS1.LINODE.COM(162.159.27.72)
lookup NS1.LINODE.COM at NS1.LINODE.COM(162.159.27.72) 21 ms
got A record 'NS1.LINODE.COM IN A 162.159.27.72' from NS1.LINODE.COM(162.159.27.72)
lookup ns2.teixido.co at NS1.LINODE.COM(162.159.27.72) 25 ms
got A record 'ns2.teixido.co IN A 162.159.24.39' from ns2.teixido.co(162.159.27.72)
lookup delsol.com.py at ns2.teixido.co(162.159.24.39) 50 ms
got A record 'delsol.com.py IN A 45.79.194.61' from delsol.com.py(162.159.24.39)
Total time: 273 ms