pazgaz.com.ua DNS Report

Health Score: 79%

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

Checked: 3 months before

Parent

NS records at parent servers

ns114.inhostedns.com
ns214.inhostedns.net
ns314.inhostedns.org
[These were obtained from ba1.ns.ua.]

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 inhostedns.com Check inhostedns.net Check inhostedns.org

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns114.inhostedns.com,ns214.inhostedns.net,ns314.inhostedns.org) at nameserver 185.104.44.36
missing A record(s) for (ns114.inhostedns.com,ns214.inhostedns.net,ns314.inhostedns.org) at nameserver 62.210.31.103

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

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

SUCCESS All the nameservers listed at the parent servers answer authoritatively for your domain.

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
hostmaster.adm.tools
Serial
2016122014
Refresh
43200
Retry
7200
Expire
604800
TTL
900

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 2016122014 at nameserver(s) (185.104.44.36 62.210.31.103)
There is serial 2016122076 at nameserver(s) (185.104.46.36)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: ns114.inhostedns.com That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2016122014 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 : 43200 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 : 7200 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 : 900 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 pazgaz.com.ua
lookup pazgaz.com.ua at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to cd1.ns.ua(194.0.1.9)
lookup pazgaz.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 pazgaz.com.ua at ba1.ns.ua(74.123.224.37) 65 ms
ba1.ns.ua(74.123.224.37) refer to ns314.inhostedns.org(unknow IP)
extra IP lookup for ns314.inhostedns.org at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns314.inhostedns.org at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d0.org.afilias-nst.org(199.19.57.1)
lookup ns314.inhostedns.org at d0.org.afilias-nst.org(199.19.57.1) 8 ms
d0.org.afilias-nst.org(199.19.57.1) refer to ns31.inhostedns.org(62.210.31.111)
lookup ns314.inhostedns.org at ns31.inhostedns.org(62.210.31.111) 86 ms
got A record 'ns314.inhostedns.org IN A 62.210.31.103' from ns314.inhostedns.org(62.210.31.111)
lookup pazgaz.com.ua at ns314.inhostedns.org(62.210.31.103) 86 ms
got A record 'pazgaz.com.ua IN A 91.206.200.104' from pazgaz.com.ua(62.210.31.103)
Total time: 322 ms