bowercapital.com DNS Report

Health Score: 66%

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

Checked: 6 months before

Parent

NS records at parent servers

nsg1.namebrightdns.com [ 34.195.64.233 34.196.114.208 34.199.213.55 34.224.202.237 ]
nsg2.namebrightdns.com [ 34.195.78.37 34.202.185.163 35.173.43.182 52.44.194.211 ]
[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.
(nsg1.namebrightdns.com.	172800	IN	A	34.195.64.233) present at Parent, missing at (34.224.202.237, 52.44.194.211)
(nsg1.namebrightdns.com.	172800	IN	A	34.196.114.208) present at Parent, missing at (34.224.202.237, 52.44.194.211)
(nsg1.namebrightdns.com.	172800	IN	A	34.199.213.55) present at Parent, missing at (34.224.202.237, 52.44.194.211)
(nsg1.namebrightdns.com.	172800	IN	A	34.224.202.237) present at Parent, missing at (34.224.202.237, 52.44.194.211)
(nsg2.namebrightdns.com.	172800	IN	A	34.195.78.37) present at Parent, missing at (34.224.202.237, 52.44.194.211)
(nsg2.namebrightdns.com.	172800	IN	A	34.202.185.163) present at Parent, missing at (34.224.202.237, 52.44.194.211)
(nsg2.namebrightdns.com.	172800	IN	A	35.173.43.182) present at Parent, missing at (34.224.202.237, 52.44.194.211)
(nsg2.namebrightdns.com.	172800	IN	A	52.44.194.211) present at Parent, missing at (34.224.202.237, 52.44.194.211)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.namebrightdns.com,ns2.namebrightdns.com) at nameserver 34.224.202.237
missing A record(s) for (ns1.namebrightdns.com,ns2.namebrightdns.com) at nameserver 52.44.194.211

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:
ns1.namebrightdns.com.
ns2.namebrightdns.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
nsg1.namebrightdns.com.
nsg2.namebrightdns.com.

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
dns.namebright.com
Serial
2018121401
Refresh
28800
Retry
5000
Expire
1209600
TTL
10800

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2018121401 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.namebrightdns.com, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2018121401 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 : 28800 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 : 5000 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 : 10800 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 bowercapital.com
lookup bowercapital.com at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup bowercapital.com at e.gtld-servers.net(192.12.94.30) 10 ms
e.gtld-servers.net(192.12.94.30) refer to nsg1.namebrightdns.com(34.195.64.233)
lookup bowercapital.com at nsg1.namebrightdns.com(34.195.64.233) 8 ms
Total time: 27 ms