sme-belgian.biz DNS Report

Health Score: 79%

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

Checked: 5 days before

Parent

NS records at parent servers

ns3.lwsdns.com
ns1.lws-hosting.biz [ 91.216.107.218 ]
ns4.lwsdns.com
ns2.lws-hosting.biz [ 185.98.131.82 ]
[These were obtained from k.gtld.biz.]

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.lws-hosting.biz.	7200	IN	A	91.216.107.218) present at Parent, missing at (91.216.107.20, 185.98.131.85)
(ns2.lws-hosting.biz.	7200	IN	A	185.98.131.82) present at Parent, missing at (91.216.107.20, 185.98.131.85)
(ns3.lwsdns.com.		21600	IN	A	91.216.107.20) present at (91.216.107.20, 185.98.131.85), missing at Parent
(ns4.lwsdns.com.		21600	IN	A	185.98.131.85) present at (91.216.107.20, 185.98.131.85), missing at Parent

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns2.lws-hosting.biz,ns1.lws-hosting.biz) at nameserver 91.216.107.20
missing A record(s) for (ns4.lwsdns.com,ns3.lwsdns.com) at nameserver 91.216.107.218
missing A record(s) for (ns1.lws-hosting.biz,ns2.lws-hosting.biz) at nameserver 185.98.131.85
missing A record(s) for (ns4.lwsdns.com,ns3.lwsdns.com) at nameserver 185.98.131.82

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.sme-belgian.biz
Serial
1523609384
Refresh
25200
Retry
3600
Expire
604800
TTL
21600

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 1523609384 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 : 25200 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 : 3600 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 : 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 sme-belgian.biz
lookup sme-belgian.biz at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld.biz(156.154.124.65)
lookup sme-belgian.biz at a.gtld.biz(156.154.124.65) 4 ms
a.gtld.biz(156.154.124.65) refer to ns1.lws-hosting.biz(91.216.107.218)
lookup sme-belgian.biz at ns1.lws-hosting.biz(91.216.107.218) 79 ms
got A record 'sme-belgian.biz IN A 91.216.107.151' from sme-belgian.biz(91.216.107.218)
Total time: 120 ms