webhost.pro DNS Report

Health Score: 84%

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

Checked: 1 year before

Parent

NS records at parent servers

ns1.dwhs.net
ns3.dwhs.net
ns2.dwhs.net
[These were obtained from a0.pro.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 dwhs.net

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 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
logs.dwhs.net
Serial
2015082843
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 2015082843 at nameserver(s) (104.223.9.2)
There is serial 2015082842 at nameserver(s) (104.225.130.130)
There is serial 2015082840 at nameserver(s) (104.223.9.254)

SOA MNAME 3/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2015082843 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 webhost.pro
lookup webhost.pro at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to b0.pro.afilias-nst.org(199.182.1.1)
lookup webhost.pro at b0.pro.afilias-nst.org(199.182.1.1) 91 ms
b0.pro.afilias-nst.org(199.182.1.1) refer to ns3.dwhs.net(unknow IP)
extra IP lookup for ns3.dwhs.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns3.dwhs.net at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns3.dwhs.net at e.gtld-servers.net(192.12.94.30) 8 ms
e.gtld-servers.net(192.12.94.30) refer to ns1.dwhs.net(104.223.9.2)
lookup ns3.dwhs.net at ns1.dwhs.net(104.223.9.2) 82 ms
got A record 'ns3.dwhs.net IN A 104.225.130.130' from ns3.dwhs.net(104.223.9.2)
lookup webhost.pro at ns3.dwhs.net(104.225.130.130) 69 ms
got A record 'webhost.pro IN A 104.223.9.6' from webhost.pro(104.225.130.130)
Total time: 259 ms