freeads-rochdale.co.uk DNS Report

Health Score: 79%

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

Checked: 1 month before

Parent

NS records at parent servers

ns1.yoursrs.com
ns2.yoursrs.com
[These were obtained from dns1.nic.uk.]

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

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns2.yoursrs.com,ns1.yoursrs.com) at nameserver 109.235.74.225
missing A record(s) for (ns2.yoursrs.com,ns1.yoursrs.com) at nameserver 167.99.193.205

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 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
hostmaster.freeads-rochdale.co.uk
Serial
2020090200
Refresh
1
Retry
1
Expire
86400
TTL
604800

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2020090200 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: ns1.yoursrs.com That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2020090200 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 : 1 seconds. This seems too small. (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 0/1

WARNING SOA Retry interval is : 1 seconds. This seems too small. (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 : 86400 seconds. This seems too small. (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 0/1

WARNING SOA Expire time is : 604800 seconds. This seems too big;. (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 freeads-rochdale.co.uk
lookup freeads-rochdale.co.uk at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to nsa.nic.uk(156.154.100.3)
lookup freeads-rochdale.co.uk at nsa.nic.uk(156.154.100.3) 46 ms
nsa.nic.uk(156.154.100.3) refer to ns1.yoursrs.com(unknow IP)
extra IP lookup for ns1.yoursrs.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.yoursrs.com at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns1.yoursrs.com at a.gtld-servers.net(192.5.6.30) 4 ms
a.gtld-servers.net(192.5.6.30) refer to sec2.rcode0.net(unknow IP)
extra IP lookup for sec2.rcode0.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup sec2.rcode0.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 sec2.rcode0.net at a.gtld-servers.net(192.5.6.30) 4 ms
a.gtld-servers.net(192.5.6.30) refer to sec1.rcode0.net(192.174.68.100)
lookup sec2.rcode0.net at sec1.rcode0.net(192.174.68.100) 18 ms
got A record 'sec2.rcode0.net IN A 176.97.158.100' from sec2.rcode0.net(192.174.68.100)
lookup ns1.yoursrs.com at sec2.rcode0.net(176.97.158.100) 5 ms
got A record 'ns1.yoursrs.com IN A 109.235.74.225' from ns1.yoursrs.com(176.97.158.100)
lookup freeads-rochdale.co.uk at ns1.yoursrs.com(109.235.74.225) 12 ms
got A record 'freeads-rochdale.co.uk IN A 161.97.99.254' from freeads-rochdale.co.uk(109.235.74.225)
Total time: 102 ms