1124.ru DNS Report

Health Score: 50%

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

Checked: 8 months before

Parent

NS records at parent servers 

ns.1124.ru [ 91.202.36.11 91.202.36.12 91.202.38.254 91.202.39.1 ]
ns.mmska.ru [ 91.202.36.11 91.202.36.12 91.202.38.254 91.202.39.1 ]
ns.waptak.com
[These were obtained from a.dns.ripn.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. 
(ns.1124.ru.		345600	IN	A	91.202.36.11) present at Parent, missing at (91.202.39.1)
(ns.1124.ru.		345600	IN	A	91.202.36.12) present at Parent, missing at (91.202.39.1)
(ns.1124.ru.		345600	IN	A	91.202.38.254) present at Parent, missing at (91.202.39.1, 91.202.36.12)
(ns.1124.ru.		345600	IN	A	91.202.39.1) present at Parent, missing at (91.202.39.1, 91.202.36.12)
(ns.mmska.ru.		345600	IN	A	91.202.36.11) present at Parent, missing at (91.202.39.1, 91.202.36.12)
(ns.mmska.ru.		345600	IN	A	91.202.36.12) present at Parent, missing at (91.202.39.1, 91.202.36.12)
(ns.mmska.ru.		345600	IN	A	91.202.38.254) present at Parent, missing at (91.202.39.1, 91.202.36.12)
(ns.mmska.ru.		345600	IN	A	91.202.39.1) present at Parent, missing at (91.202.39.1, 91.202.36.12)

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (ns.mmska.ru,ns.waptak.com) at nameserver 91.202.36.12

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (91.202.39.1) there are nameservers:
At (91.202.36.12) there are nameservers: ns.1124.ru. ns.mmska.ru. ns.waptak.com.

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

Lame nameservers: 
91.202.39.1

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
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.202.39.1)
There is serial 2016060918 at nameserver(s) (91.202.36.12)

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 1124.ru
lookup 1124.ru at A.ROOT-SERVERS.NET(198.41.0.4) 42 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup 1124.ru at a.dns.ripn.net(193.232.128.6) 118 ms
a.dns.ripn.net(193.232.128.6) refer to ns.1124.ru(91.202.36.11)
lookup 1124.ru at ns.1124.ru(91.202.36.11) 120 ms
got A record '1124.ru IN A 91.202.36.253' from 1124.ru(91.202.36.11)
Total time: 280 ms