abc.com.py DNS Report

Health Score: 89%

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

Checked: 3 days before

Parent

NS records at parent servers

dns2.abc.com.py
dns1.abc.com.py
[These were obtained from b.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

SUCCESS The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.

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 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
alerojas.abc.COM.PY
Serial
2009211036
Refresh
1200
Retry
120
Expire
604800
TTL
60

Serial agreement 7/7

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

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: dns1.abc.COM.PY That server is listed at the parent servers, which is correct.

Serial value 1/1

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

WARNING SOA Expire time is : 60 seconds. This seems too small. (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 abc.COM.PY
lookup abc.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 abc.COM.PY at b.dns.PY(200.160.0.5) 127 ms
b.dns.PY(200.160.0.5) refer to dns2.abc.com.py(unknow IP)
extra IP lookup for dns2.abc.com.py at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns2.abc.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 dns2.abc.com.py at b.dns.py(200.160.0.5) 126 ms
b.dns.py(200.160.0.5) refer to dns1.abc.com.py(unknow IP)
extra IP lookup for dns1.abc.com.py at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns1.abc.com.py at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to b.dns.py(200.160.0.5)
lookup dns1.abc.com.py at b.dns.py(200.160.0.5) 144 ms
b.dns.py(200.160.0.5) refer to dns1.abc.com.py(unknow IP)
extra IP lookup for dns1.abc.com.py at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns1.abc.com.py at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to p.dns.py(204.61.216.107)
lookup dns1.abc.com.py at p.dns.py(204.61.216.107) 3 ms
p.dns.py(204.61.216.107) refer to dns2.abc.com.py(200.3.249.87)
lookup dns1.abc.com.py at dns2.abc.com.py(200.3.249.87) 187 ms
got A record 'dns1.abc.com.py IN A 201.217.5.250' from dns1.abc.com.py(200.3.249.87)
lookup dns1.abc.com.py at dns1.abc.com.py(201.217.5.250) 179 ms
got A record 'dns1.abc.com.py IN A 201.217.5.250' from dns1.abc.com.py(201.217.5.250)
lookup dns2.abc.com.py at dns1.abc.com.py(201.217.5.250) 179 ms
got A record 'dns2.abc.com.py IN A 200.3.249.87' from dns2.abc.com.py(201.217.5.250)
lookup abc.COM.PY at dns2.abc.com.py(200.3.249.87) 194 ms
got A record 'abc.COM.PY IN A 186.182.80.50' from abc.COM.PY(200.3.249.87)
Total time: 1154 ms