serverfreak.biz DNS Report

Health Score: 71%

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

Checked: 1 year before

Parent

NS records at parent servers

ns3.linode.com
ns5.linode.com
ns2.serverfreak.biz [ 202.75.35.162 ]
ns1.serverfreak.biz [ 72.9.157.209 ]
ns4.linode.com
ns2.linode.com
ns1.linode.com
[These were obtained from a.gtld.biz.]

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 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns1.linode.com.		300	IN	A	162.159.27.72) present at (162.159.25.129, 162.159.24.25, 162.159.26.99, 162.159.24.39, 162.159.27.72), missing at Parent
(ns2.linode.com.		300	IN	A	162.159.24.39) present at (162.159.25.129, 162.159.24.25, 162.159.26.99, 162.159.24.39, 162.159.27.72), missing at Parent
(ns3.linode.com.		300	IN	A	162.159.25.129) present at (162.159.25.129, 162.159.24.25, 162.159.26.99, 162.159.24.39, 162.159.27.72), missing at Parent
(ns4.linode.com.		300	IN	A	162.159.26.99) present at (162.159.25.129, 162.159.24.25, 162.159.26.99, 162.159.24.39, 162.159.27.72), missing at Parent
(ns5.linode.com.		300	IN	A	162.159.24.25) present at (162.159.25.129, 162.159.24.25, 162.159.26.99, 162.159.24.39, 162.159.27.72), missing at Parent

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns5.linode.com,ns1.linode.com,ns2.linode.com,ns3.linode.com,ns4.linode.com) at nameserver 202.75.35.162
missing A record(s) for (ns3.linode.com,ns2.linode.com,ns1.linode.com,ns5.linode.com,ns4.linode.com) at nameserver 72.9.157.209

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 7 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
domreg.serverfreak.com
Serial
2017062041
Refresh
14400
Retry
14400
Expire
1209600
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 2017062041 at nameserver(s) (162.159.25.129 162.159.24.25 162.159.26.99 162.159.24.39 162.159.27.72)
There is serial 2017062001 at nameserver(s) (202.75.35.162 72.9.157.209)

SOA MNAME 3/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2017062041 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 : 14400 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 0/1

WARNING SOA Retry interval is : 14400 seconds. This seems too big;. (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 : 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 serverfreak.biz
lookup serverfreak.biz at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld.biz(156.154.124.65)
lookup serverfreak.biz at a.gtld.biz(156.154.124.65) 4 ms
a.gtld.biz(156.154.124.65) refer to ns1.serverfreak.biz(72.9.157.209)
lookup serverfreak.biz at ns1.serverfreak.biz(72.9.157.209) 44 ms
got A record 'serverfreak.biz IN A 104.199.179.221' from serverfreak.biz(72.9.157.209)
Total time: 51 ms