qerrassa.net DNS Report

Health Score: 85%

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

Checked: 6 days before

Parent

NS records at parent servers

ns1.dnsowl.com [ 104.160.191.84 158.69.102.53 158.69.21.172 172.106.13.60 172.106.7.203 185.34.216.59 198.251.84.105 204.188.236.36 37.187.179.91 45.63.106.63 45.63.5.234 92.222.189.157 95.183.53.28 ]
ns2.dnsowl.com [ 104.143.9.16 104.207.141.138 107.191.99.216 142.4.203.33 164.132.182.29 167.114.213.239 198.251.81.178 45.35.51.101 45.35.72.169 45.58.188.56 45.63.62.227 5.196.27.156 51.255.211.175 ]
ns3.dnsowl.com
[These were obtained from a.gtld-servers.net.]

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

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns1.dnsowl.com.		172800	IN	A	104.160.191.84) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	158.69.102.53) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	158.69.21.172) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	172.106.13.60) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	198.251.84.105) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	204.188.236.36) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	45.63.106.63) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	45.63.5.234) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	92.222.189.157) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns1.dnsowl.com.		172800	IN	A	95.183.53.28) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	142.4.203.33) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	164.132.182.29) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	167.114.213.239) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	198.251.81.178) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	45.35.51.101) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	45.35.72.169) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	45.58.188.56) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	45.63.62.227) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	5.196.27.156) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns2.dnsowl.com.		172800	IN	A	51.255.211.175) present at Parent, missing at (95.183.53.28, 51.255.211.175, 198.251.80.184)
(ns3.dnsowl.com.		32400	IN	A	158.69.33.230) present at (95.183.53.28, 51.255.211.175, 198.251.80.184), missing at Parent
(ns3.dnsowl.com.		21600	IN	A	198.251.80.184) present at (95.183.53.28, 51.255.211.175, 198.251.80.184), missing at Parent
(ns3.dnsowl.com.		43200	IN	A	70.39.65.12) present at (95.183.53.28, 51.255.211.175, 198.251.80.184), missing at Parent

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

SUCCESS You have 3 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.dnsowl.com
Serial
1497915159
Refresh
7200
Retry
1800
Expire
1209600
TTL
172800

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 1497915159 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 : 7200 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 : 1800 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 0/1

WARNING SOA Expire time is : 172800 seconds. This seems too big;. (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 qerrassa.net
lookup qerrassa.net at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup qerrassa.net at a.gtld-servers.net(192.5.6.30) 9 ms
a.gtld-servers.net(192.5.6.30) refer to ns1.dnsowl.com(104.160.191.84)
lookup qerrassa.net at ns1.dnsowl.com(104.160.191.84) 94 ms
got A record 'qerrassa.net IN A 95.85.20.48' from qerrassa.net(104.160.191.84)
Total time: 106 ms