ekaternia.org DNS Report

Health Score: 47%

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

Checked: 11 months before


NS records at parent servers

[These were obtained from a0.org.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


Mismatched glue 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check ovh.net Check ip-188-165-216.eu

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 ( there are nameservers:
At ( there are nameservers: ns.ekaternia.org.

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:

Missing (stealth) nameservers 0/7

DANGER There are nameservers not listed at the parent servers:

Root missing nameservers 0/7

DANGER There are nameservers not listed 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 record

SOA record is:
Hostmaster email

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 at nameserver(s) (
There is serial 1511541458 at nameserver(s) (


DANGER SOA (Start of Authority) record states that your master (primary) name server is: , but that server is not listed at the parent servers.

Serial value 0/1

WARNING SOA serial number is: This not 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 0/1

WARNING SOA Retry interval is : seconds. This seems too small. (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 0/1

WARNING SOA Retry interval is : seconds. This seems too small. (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 0/1

WARNING SOA Expire time is : seconds. This seems too small. (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 : seconds. This seems too small. (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.


DNS trace

Trace to ekaternia.org
lookup ekaternia.org at A.ROOT-SERVERS.NET( 15 ms
A.ROOT-SERVERS.NET( refer to a0.org.afilias-nst.info(
lookup ekaternia.org at a0.org.afilias-nst.info( 170 ms
a0.org.afilias-nst.info( refer to ns366816.ip-188-165-216.eu(unknow IP)
extra IP lookup for ns366816.ip-188-165-216.eu at root server A.ROOT-SERVERS.NET(
lookup ns366816.ip-188-165-216.eu at A.ROOT-SERVERS.NET( 12 ms
A.ROOT-SERVERS.NET( refer to cz.dns.eu(
lookup ns366816.ip-188-165-216.eu at cz.dns.eu( 114 ms
cz.dns.eu( refer to dns100.ovh.net(unknow IP)
extra IP lookup for dns100.ovh.net at root server A.ROOT-SERVERS.NET(
lookup dns100.ovh.net at A.ROOT-SERVERS.NET( 13 ms
A.ROOT-SERVERS.NET( refer to a.gtld-servers.net(
lookup dns100.ovh.net at a.gtld-servers.net( 12 ms
a.gtld-servers.net( refer to ns10.ovh.net(
lookup dns100.ovh.net at ns10.ovh.net( 77 ms
got A record 'dns100.ovh.net IN A' from dns100.ovh.net(
lookup ns366816.ip-188-165-216.eu at dns100.ovh.net( 72 ms
got A record 'ns366816.ip-188-165-216.eu IN A' from ns366816.ip-188-165-216.eu(
lookup ekaternia.org at ns366816.ip-188-165-216.eu( 78 ms
got A record 'ekaternia.org IN A' from ekaternia.org(
Total time: 563 ms