wewashwindows.net DNS Report

Health Score: 85%

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

Checked: 3 days before

Parent

NS records at parent servers

ns-cloud-a1.googledomains.com [ 216.239.32.106 ]
ns-cloud-a2.googledomains.com [ 216.239.34.106 ]
ns-cloud-a3.googledomains.com [ 216.239.36.106 ]
ns-cloud-a4.googledomains.com [ 216.239.38.106 ]
[These were obtained from e.gtld-servers.net.]

Glue at parent nameservers 7/7

SUCCESS Parent nameservers know A records for your domain, Very good !

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns-cloud-a1.googledomains.com.	172800	IN	A	216.239.32.106) present at Parent, missing at (216.239.32.106, 216.239.34.106, 216.239.36.106, 216.239.38.106)
(ns-cloud-a2.googledomains.com.	172800	IN	A	216.239.34.106) present at Parent, missing at (216.239.32.106, 216.239.34.106, 216.239.36.106, 216.239.38.106)
(ns-cloud-a3.googledomains.com.	172800	IN	A	216.239.36.106) present at Parent, missing at (216.239.32.106, 216.239.34.106, 216.239.36.106, 216.239.38.106)
(ns-cloud-a4.googledomains.com.	172800	IN	A	216.239.38.106) present at Parent, missing at (216.239.32.106, 216.239.34.106, 216.239.36.106, 216.239.38.106)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns-cloud-a1.googledomains.com,ns-cloud-a2.googledomains.com,ns-cloud-a3.googledomains.com,ns-cloud-a4.googledomains.com) at nameserver 216.239.32.106
missing A record(s) for (ns-cloud-a1.googledomains.com,ns-cloud-a2.googledomains.com,ns-cloud-a3.googledomains.com,ns-cloud-a4.googledomains.com) at nameserver 216.239.34.106
missing A record(s) for (ns-cloud-a1.googledomains.com,ns-cloud-a2.googledomains.com,ns-cloud-a3.googledomains.com,ns-cloud-a4.googledomains.com) at nameserver 216.239.36.106
missing A record(s) for (ns-cloud-a1.googledomains.com,ns-cloud-a2.googledomains.com,ns-cloud-a3.googledomains.com,ns-cloud-a4.googledomains.com) at nameserver 216.239.38.106

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 4 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
cloud-dns-hostmaster.google.com
Serial
14
Refresh
21600
Retry
3600
Expire
1209600
TTL
21600

Serial agreement 7/7

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

SOA MNAME 3/3

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

Serial value 0/1

WARNING SOA serial number is: 14 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 1/1

SUCCESS SOA Retry interval is : 21600 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 : 3600 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 : 21600 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 wewashwindows.net
lookup wewashwindows.net at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup wewashwindows.net at a.gtld-servers.net(192.5.6.30) 16 ms
a.gtld-servers.net(192.5.6.30) refer to ns-cloud-a1.googledomains.com(216.239.32.106)
lookup wewashwindows.net at ns-cloud-a1.googledomains.com(216.239.32.106) 61 ms
got A record 'wewashwindows.net IN A 162.243.96.63' from wewashwindows.net(216.239.32.106)
Total time: 81 ms