91w.vc DNS Report

Health Score: 73%

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

Checked: 3 months before

Parent

NS records at parent servers

ns4.myhostadmin.net
ns3.myhostadmin.net
[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 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check myhostadmin.net

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns2.myhostadmin.net,ns3.myhostadmin.net,ns4.myhostadmin.net,ns5.myhostadmin.net,ns6.myhostadmin.net,ns1.myhostadmin.net) at nameserver 113.17.175.200
missing A record(s) for (ns4.myhostadmin.net,ns5.myhostadmin.net,ns6.myhostadmin.net,ns1.myhostadmin.net,ns2.myhostadmin.net,ns3.myhostadmin.net) at nameserver 113.17.175.150

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

DANGER There are nameservers not listed at the parent servers:
ns2.myhostadmin.net.
ns5.myhostadmin.net.
ns6.myhostadmin.net.
ns1.myhostadmin.net.

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
dnsconct.myhostadmin.net
Serial
2017062211
Refresh
43200
Retry
300
Expire
1209600
TTL
500

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2017062211 That means that all your nameservers are using the same data.

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: ns1.myhostadmin.net, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2017062211 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 : 300 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 : 1209600 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 : 500 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 91w.vc
lookup 91w.vc at A.ROOT-SERVERS.NET(198.41.0.4) 19 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.cctld.afilias-nst.info(199.254.59.1)
lookup 91w.vc at a0.cctld.afilias-nst.info(199.254.59.1) 159 ms
a0.cctld.afilias-nst.info(199.254.59.1) refer to ns4.myhostadmin.net(unknow IP)
extra IP lookup for ns4.myhostadmin.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns4.myhostadmin.net at A.ROOT-SERVERS.NET(198.41.0.4) 20 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns4.myhostadmin.net at e.gtld-servers.net(192.12.94.30) 30 ms
e.gtld-servers.net(192.12.94.30) refer to ns1.myhostadmin.net(113.17.175.150)
lookup ns4.myhostadmin.net at ns1.myhostadmin.net(113.17.175.150) 275 ms
got A record 'ns4.myhostadmin.net IN A 113.17.175.200' from ns4.myhostadmin.net(113.17.175.150)
lookup 91w.vc at ns4.myhostadmin.net(113.17.175.200) 246 ms
got A record '91w.vc IN A 162.251.93.34' from 91w.vc(113.17.175.200)
Total time: 749 ms