semos-online.eu 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

dns-05.semos-online.eu [ 81.17.229.154 ]
dns-02.semos-online.eu [ 81.17.229.140 ]
dns-01.semos-online.eu [ 81.17.229.150 ]
dns-03.semos-online.eu [ 81.17.229.152 ]
dns-04.semos-online.eu [ 81.17.229.153 ]
[These were obtained from x.dns.eu.]

Glue at parent nameservers 7/7

SUCCESS Parent nameservers know A records for your domain, Very good !

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(dns-01.semos-online.eu.	86400	IN	A	81.17.229.150) present at Parent, missing at (81.17.229.153)
(dns-02.semos-online.eu.	86400	IN	A	81.17.229.140) present at Parent, missing at (81.17.229.153)
(dns-03.semos-online.eu.	86400	IN	A	81.17.229.152) present at Parent, missing at (81.17.229.153)
(dns-04.semos-online.eu.	86400	IN	A	81.17.229.153) present at Parent, missing at (81.17.229.153)
(dns-05.semos-online.eu.	86400	IN	A	81.17.229.154) present at Parent, missing at (81.17.229.153)

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

The NS records at your nameservers are different
At (81.17.229.140 81.17.229.150) there are nameservers: dns-03.semos-online.eu. dns-02.semos-online.eu. dns-04.semos-online.eu. dns-01.semos-online.eu. dns-05.semos-online.eu.
At (81.17.229.153) there are nameservers:

Nameservers respond 0/10

Some nameservers does not respond:
81.17.229.154
81.17.229.152

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 5 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:
81.17.229.153

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
zagreb-01.semos-online.eu
Serial
2017051111
Refresh
14400
Retry
1800
Expire
604800
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 2017051111 at nameserver(s) (81.17.229.140 81.17.229.150)
There is serial at nameserver(s) (81.17.229.153)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: dns-01.semos-online.eu That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2017051111 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 : 14400 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 : 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 semos-online.eu
lookup semos-online.eu at A.ROOT-SERVERS.NET(198.41.0.4) 7 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to cz.dns.eu(93.190.128.138)
lookup semos-online.eu at cz.dns.eu(93.190.128.138) 100 ms
cz.dns.eu(93.190.128.138) refer to dns-02.semos-online.eu(81.17.229.140)
lookup semos-online.eu at dns-02.semos-online.eu(81.17.229.140) 118 ms
got A record 'semos-online.eu IN A 81.17.229.150' from semos-online.eu(81.17.229.140)
Total time: 225 ms