Need help fixing DNS ? Get an expert advise at
support forum
Checked: 1 week before
Parent
NS records at parent servers
ns1.hostinger.com.br
ns2.hostinger.com.br
[These were obtained from a.dns.br.]
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 hostinger.com.br
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
0/7
DANGER
There are nameservers not listed at the parent servers:
ns4.hostinger.com.br.
ns3.hostinger.com.br.
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.microone.com.br
Serial
2016121213
Refresh
28800
Retry
7200
Expire
604800
TTL
86400
Serial agreement
7/7
SUCCESS
All your nameservers agree that your SOA serial number is 2016121213 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: ns1.hostinger.com.br That server is listed at the parent servers, which is correct.
Serial value
1/1
SUCCESS
SOA serial number is: 2016121213 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 : 28800 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
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
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 microone.com.br
lookup microone.com.br at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to f.dns.br(200.219.159.10)
lookup microone.com.br at f.dns.br(200.219.159.10) 195 ms
f.dns.br(200.219.159.10) refer to ns2.hostinger.com.br(unknow IP)
extra IP lookup for ns2.hostinger.com.br at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.hostinger.com.br at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.br(200.160.0.10)
lookup ns2.hostinger.com.br at a.dns.br(200.160.0.10) 127 ms
a.dns.br(200.160.0.10) refer to any2.hostinger.com(unknow IP)
extra IP lookup for any2.hostinger.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup any2.hostinger.com at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup any2.hostinger.com at e.gtld-servers.net(192.12.94.30) 9 ms
e.gtld-servers.net(192.12.94.30) refer to any1.hostinger.com(153.92.2.8)
lookup any2.hostinger.com at any1.hostinger.com(153.92.2.8) 79 ms
got A record 'any2.hostinger.com IN A 153.92.2.9' from any2.hostinger.com(153.92.2.8)
lookup ns2.hostinger.com.br at any2.hostinger.com(153.92.2.9) 80 ms
got A record 'ns2.hostinger.com.br IN A 31.220.23.1' from ns2.hostinger.com.br(153.92.2.9)
lookup microone.com.br at ns2.hostinger.com.br(31.220.23.1) 81 ms
got A record 'microone.com.br IN A 185.28.21.137' from microone.com.br(31.220.23.1)