sushi-club.me DNS Report

Health Score: 47%

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

Checked: 2 months before

Parent

NS records at parent servers

ns9.rehost.com.ua
ns10.rehost.com.ua
[These were obtained from a0.nic.me.]

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 rehost.com.ua

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 (91.194.250.188) there are nameservers:
At (193.151.90.123) there are nameservers: ns7.rehost.com.ua. ns8.rehost.com.ua.

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:
91.194.250.188

Missing (stealth) nameservers 0/7

DANGER There are nameservers not listed at the parent servers:
ns7.rehost.com.ua.
ns8.rehost.com.ua.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns9.rehost.com.ua.
ns10.rehost.com.ua.

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
Serial
Refresh
Retry
Expire
TTL

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

SOA MNAME 0/3

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.

Info

DNS trace

Trace to sushi-club.me
lookup sushi-club.me at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to c0.nic.me(199.253.61.1)
lookup sushi-club.me at c0.nic.me(199.253.61.1) 159 ms
c0.nic.me(199.253.61.1) refer to ns10.rehost.com.ua(unknow IP)
extra IP lookup for ns10.rehost.com.ua at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns10.rehost.com.ua at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to cd1.ns.ua(194.0.1.9)
lookup ns10.rehost.com.ua at cd1.ns.ua(194.0.1.9) 3 ms
cd1.ns.ua(194.0.1.9) refer to ba1.ns.ua(74.123.224.37)
lookup ns10.rehost.com.ua at ba1.ns.ua(74.123.224.37) 65 ms
ba1.ns.ua(74.123.224.37) refer to tess.ns.cloudflare.com(unknow IP)
extra IP lookup for tess.ns.cloudflare.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup tess.ns.cloudflare.com at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup tess.ns.cloudflare.com at e.gtld-servers.net(192.12.94.30) 11 ms
e.gtld-servers.net(192.12.94.30) refer to ns3.cloudflare.com(162.159.0.33)
lookup tess.ns.cloudflare.com at ns3.cloudflare.com(162.159.0.33) 3 ms
got A record 'tess.ns.cloudflare.com IN A 173.245.58.227' from tess.ns.cloudflare.com(162.159.0.33)
lookup ns10.rehost.com.ua at tess.ns.cloudflare.com(173.245.58.227) 3 ms
got A record 'ns10.rehost.com.ua IN A 193.151.90.123' from ns10.rehost.com.ua(173.245.58.227)
lookup sushi-club.me at ns10.rehost.com.ua(193.151.90.123) 84 ms
got A record 'sushi-club.me IN A 91.194.250.152' from sushi-club.me(193.151.90.123)
Total time: 356 ms