zohanteam.it DNS Report

Health Score: 83%

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

Checked: 1 month before

Parent

NS records at parent servers 

dns3.arubadns.net
dns.technorail.com
dns4.arubadns.cz
dns2.technorail.com
[These were obtained from r.dns.it.]

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 arubadns.net Check technorail.com Check arubadns.cz

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (dns2.technorail.com,dns3.arubadns.net,dns.technorail.com,dns4.arubadns.cz) at nameserver 95.110.220.5
missing A record(s) for (dns.technorail.com,dns3.arubadns.net,dns4.arubadns.cz,dns2.technorail.com) at nameserver 94.177.210.13
missing A record(s) for (dns.technorail.com,dns3.arubadns.net,dns4.arubadns.cz,dns2.technorail.com) at nameserver 81.2.216.125
missing A record(s) for (dns3.arubadns.net,dns2.technorail.com,dns4.arubadns.cz,dns.technorail.com) at nameserver 95.110.136.8

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 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.technorail.com
Serial
1
Refresh
86400
Retry
7200
Expire
2592000
TTL
21600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 1 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: dns.technorail.com That server is listed at the parent servers, which is correct.

Serial value 0/1

WARNING SOA serial number is: 1 This not 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 : 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 : 21600 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 zohanteam.it
lookup zohanteam.it at A.ROOT-SERVERS.NET(198.41.0.4) 6 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to r.dns.it(193.206.141.46)
lookup zohanteam.it at r.dns.it(193.206.141.46) 37 ms
r.dns.it(193.206.141.46) refer to dns3.arubadns.net(unknow IP)
extra IP lookup for dns3.arubadns.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns3.arubadns.net 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 dns3.arubadns.net at a.gtld-servers.net(192.5.6.30) 5 ms
a.gtld-servers.net(192.5.6.30) refer to arudns4.aruba.it(unknow IP)
extra IP lookup for arudns4.aruba.it at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup arudns4.aruba.it at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.it(194.0.16.215)
lookup arudns4.aruba.it at a.dns.it(194.0.16.215) 4 ms
a.dns.it(194.0.16.215) refer to arudns2.aruba.it(62.149.132.7)
lookup arudns4.aruba.it at arudns2.aruba.it(62.149.132.7) 33 ms
got A record 'arudns4.aruba.it IN A 81.2.199.97' from arudns4.aruba.it(62.149.132.7)
lookup dns3.arubadns.net at arudns4.aruba.it(81.2.199.97) 31 ms
got A record 'dns3.arubadns.net IN A 95.110.220.5' from dns3.arubadns.net(81.2.199.97)
lookup zohanteam.it at dns3.arubadns.net(95.110.220.5) 34 ms
got A record 'zohanteam.it IN A 89.46.106.50' from zohanteam.it(95.110.220.5)
Total time: 163 ms