socialtool.info DNS Report

Health Score: 62%

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

Checked: 1 week before

Parent

NS records at parent servers

vps136710.vps.ovh.ca
sdns1.ovh.ca
[These were obtained from a0.info.afilias-nst.info.]

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 vps.ovh.ca Check ovh.ca

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (sdns1.ovh.ca,vps136710.vps.ovh.ca) at nameserver 158.69.208.21

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (158.69.208.21) there are nameservers: sdns1.ovh.ca. vps136710.vps.ovh.ca.
At (8.33.137.137) there are nameservers:

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

Lame nameservers:
8.33.137.137

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
emmalaurencez.gmail.com
Serial
2017081804
Refresh
3600
Retry
7200
Expire
1209600
TTL
86400

Serial agreement 0/7

DANGER Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
There is serial 2017081804 at nameserver(s) (158.69.208.21)
There is serial at nameserver(s) (8.33.137.137)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: vps136710.vps.ovh.ca That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2017081804 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 : 3600 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 : 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 socialtool.info
lookup socialtool.info at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a2.info.afilias-nst.info(199.249.113.1)
lookup socialtool.info at a2.info.afilias-nst.info(199.249.113.1) 2 ms
a2.info.afilias-nst.info(199.249.113.1) refer to vps136710.vps.ovh.ca(unknow IP)
extra IP lookup for vps136710.vps.ovh.ca at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup vps136710.vps.ovh.ca at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to any.ca-servers.ca(199.4.144.2)
lookup vps136710.vps.ovh.ca at any.ca-servers.ca(199.4.144.2) 75 ms
any.ca-servers.ca(199.4.144.2) refer to ns19.ovh.net(unknow IP)
extra IP lookup for ns19.ovh.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns19.ovh.net at A.ROOT-SERVERS.NET(198.41.0.4) 6 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns19.ovh.net at e.gtld-servers.net(192.12.94.30) 44 ms
e.gtld-servers.net(192.12.94.30) refer to ns10.ovh.net(213.251.128.129)
lookup ns19.ovh.net at ns10.ovh.net(213.251.128.129) 74 ms
got A record 'ns19.ovh.net IN A 213.251.128.139' from ns19.ovh.net(213.251.128.129)
lookup vps136710.vps.ovh.ca at ns19.ovh.net(213.251.128.139) 73 ms
ns19.ovh.net(213.251.128.139) refer to dns10.ovh.ca(8.33.137.161)
lookup vps136710.vps.ovh.ca at dns10.ovh.ca(8.33.137.161) 14 ms
got A record 'vps136710.vps.ovh.ca IN A 158.69.208.21' from vps136710.vps.ovh.ca(8.33.137.161)
lookup socialtool.info at vps136710.vps.ovh.ca(158.69.208.21) 12 ms
got A record 'socialtool.info IN A 158.69.208.21' from socialtool.info(158.69.208.21)
Total time: 309 ms