sharyngol.mn DNS Report

Health Score: 50%

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

Checked: 1 week before

Parent

NS records at parent servers

ns1.justhost.com
ns1.itools.mn [ 43.231.112.15 ]
ns2.itools.mn [ 43.231.112.16 ]
ns3.itools.mn [ 104.236.107.28 ]
ns2.justhost.com
[These were obtained from a0.cctld.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

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns1.itools.mn.		86400	IN	A	43.231.112.15) present at Parent, missing at (162.159.24.49, 162.159.25.241)
(ns2.itools.mn.		86400	IN	A	43.231.112.16) present at Parent, missing at (162.159.24.49, 162.159.25.241)
(ns3.itools.mn.		86400	IN	A	104.236.107.28) present at Parent, missing at (162.159.24.49, 162.159.25.241)

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 (162.159.24.49 162.159.25.241) there are nameservers:
At (43.231.112.15 43.231.112.16 104.236.107.28) there are nameservers: ns1.itools.mn. ns3.itools.mn. ns2.itools.mn.

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 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:
162.159.24.49
162.159.25.241

Missing (stealth) nameservers 7/7

SUCCESS All your nameservers are also listed at the parent servers.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns1.justhost.com.
ns2.justhost.com.

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) (162.159.24.49 162.159.25.241)
There is serial 2016092202 at nameserver(s) (43.231.112.15 43.231.112.16 104.236.107.28)

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 sharyngol.mn
lookup sharyngol.mn at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.cctld.afilias-nst.info(199.254.59.1)
lookup sharyngol.mn at a0.cctld.afilias-nst.info(199.254.59.1) 162 ms
a0.cctld.afilias-nst.info(199.254.59.1) refer to ns3.itools.mn(104.236.107.28)
lookup sharyngol.mn at ns3.itools.mn(104.236.107.28) 6 ms
got A record 'sharyngol.mn IN A 43.231.112.46' from sharyngol.mn(104.236.107.28)
Total time: 173 ms