qtech.vn DNS Report

Health Score: 81%

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

Checked: 1 day before

Parent

NS records at parent servers

dns4.vina-host.com
dns3.vina-host.com
[These were obtained from f.dns-servers.vn.]

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 vina-host.com

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 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 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 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
root.dns3.vina-host.vn
Serial
2015110805
Refresh
86400
Retry
7200
Expire
3600000
TTL
86400

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 2015110805 at nameserver(s) (123.30.129.227)
There is serial 2013091004 at nameserver(s) (125.212.217.195)

SOA MNAME 3/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2015110805 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 0/1

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

WARNING SOA Expire time is : 3600000 seconds. This seems too big;. (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 : 86400 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 qtech.vn
lookup qtech.vn at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns-servers.vn(194.0.1.18)
lookup qtech.vn at a.dns-servers.vn(194.0.1.18) 66 ms
a.dns-servers.vn(194.0.1.18) refer to dns4.vina-host.com(unknow IP)
extra IP lookup for dns4.vina-host.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns4.vina-host.com at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to m.gtld-servers.net(192.55.83.30)
lookup dns4.vina-host.com at m.gtld-servers.net(192.55.83.30) 128 ms
m.gtld-servers.net(192.55.83.30) refer to ns1.vinahost.vn(unknow IP)
extra IP lookup for ns1.vinahost.vn at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.vinahost.vn at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to f.dns-servers.vn(203.119.68.105)
lookup ns1.vinahost.vn at f.dns-servers.vn(203.119.68.105) 257 ms
f.dns-servers.vn(203.119.68.105) refer to demi.ns.cloudflare.com(unknow IP)
extra IP lookup for demi.ns.cloudflare.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup demi.ns.cloudflare.com at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to m.gtld-servers.net(192.55.83.30)
lookup demi.ns.cloudflare.com at m.gtld-servers.net(192.55.83.30) 128 ms
m.gtld-servers.net(192.55.83.30) refer to ns3.cloudflare.com(162.159.0.33)
lookup demi.ns.cloudflare.com at ns3.cloudflare.com(162.159.0.33) 3 ms
got A record 'demi.ns.cloudflare.com IN A 173.245.58.95' from demi.ns.cloudflare.com(162.159.0.33)
lookup ns1.vinahost.vn at demi.ns.cloudflare.com(173.245.58.95) 3 ms
got A record 'ns1.vinahost.vn IN A 123.30.137.108' from ns1.vinahost.vn(173.245.58.95)
lookup dns4.vina-host.com at ns1.vinahost.vn(123.30.137.108) 260 ms
got A record 'dns4.vina-host.com IN A 123.30.129.227' from dns4.vina-host.com(123.30.137.108)
lookup qtech.vn at dns4.vina-host.com(123.30.129.227) 249 ms
got A record 'qtech.vn IN A 123.30.129.231' from qtech.vn(123.30.129.227)
Total time: 1107 ms