photographylessons.club DNS Report

Health Score: 64%

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

Checked: 6 months before

Parent

NS records at parent servers

ns465.websitewelcome.com
ns466.websitewelcome.com
[These were obtained from ns1.dns.nic.club.]

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 websitewelcome.com

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (dns1.registrar-servers.com,dns2.registrar-servers.com) at nameserver 192.185.92.172
missing A record(s) for (dns1.registrar-servers.com,dns2.registrar-servers.com) at nameserver 192.185.92.173

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:
dns1.registrar-servers.com.
dns2.registrar-servers.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns465.websitewelcome.com.
ns466.websitewelcome.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
hostingsitedeals.yahoo.com
Serial
2018022103
Refresh
86400
Retry
7200
Expire
3600000
TTL
86400

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2018022103 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 photographylessons.club
lookup photographylessons.club at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns1.dns.nic.club(156.154.144.215)
lookup photographylessons.club at ns1.dns.nic.club(156.154.144.215) 10 ms
ns1.dns.nic.club(156.154.144.215) refer to ns466.websitewelcome.com(unknow IP)
extra IP lookup for ns466.websitewelcome.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns466.websitewelcome.com at A.ROOT-SERVERS.NET(198.41.0.4) 17 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns466.websitewelcome.com at a.gtld-servers.net(192.5.6.30) 8 ms
a.gtld-servers.net(192.5.6.30) refer to ns1.p13.dynect.net(208.78.70.13)
lookup ns466.websitewelcome.com at ns1.p13.dynect.net(208.78.70.13) 10 ms
got A record 'ns466.websitewelcome.com IN A 192.185.92.173' from ns466.websitewelcome.com(208.78.70.13)
lookup photographylessons.club at ns466.websitewelcome.com(192.185.92.173) 69 ms
got A record 'photographylessons.club IN A 192.185.14.196' from photographylessons.club(192.185.92.173)
Total time: 125 ms