1stpro.info DNS Report

Health Score: 65%

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

Checked: 3 months before

Parent

NS records at parent servers

ns2.crazydomains.com.au
ns1.crazydomains.com.au
[These were obtained from a0.info.afilias-nst.info.]

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 crazydomains.com.au

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns2.crazydomains.com,ns1.crazydomains.com) at nameserver 27.124.125.8
missing A record(s) for (ns2.crazydomains.com,ns1.crazydomains.com) at nameserver 27.124.125.7

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

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns2.crazydomains.com.au.
ns1.crazydomains.com.au.

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
admin.syrahost.com
Serial
1512358484
Refresh
3600
Retry
7200
Expire
3600000
TTL
3600

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 1512358484 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 : 3600 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 : 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 : 3600 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 1stpro.info
lookup 1stpro.info at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.info.afilias-nst.info(199.254.31.1)
lookup 1stpro.info at a0.info.afilias-nst.info(199.254.31.1) 159 ms
a0.info.afilias-nst.info(199.254.31.1) refer to ns2.crazydomains.com.au(unknow IP)
extra IP lookup for ns2.crazydomains.com.au at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.crazydomains.com.au at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.au(58.65.254.73)
lookup ns2.crazydomains.com.au at a.au(58.65.254.73) 95 ms
a.au(58.65.254.73) refer to w.au(37.209.192.5)
lookup ns2.crazydomains.com.au at w.au(37.209.192.5) 80 ms
w.au(37.209.192.5) refer to names1.syrahost.com(unknow IP)
extra IP lookup for names1.syrahost.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup names1.syrahost.com at A.ROOT-SERVERS.NET(198.41.0.4) 13 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup names1.syrahost.com at a.gtld-servers.net(192.5.6.30) 9 ms
a.gtld-servers.net(192.5.6.30) refer to names1.syrahost.com(27.124.125.3)
lookup names1.syrahost.com at names1.syrahost.com(27.124.125.3) 273 ms
got A record 'names1.syrahost.com IN A 27.124.125.3' from names1.syrahost.com(27.124.125.3)
lookup ns2.crazydomains.com.au at names1.syrahost.com(27.124.125.3) 274 ms
got A record 'ns2.crazydomains.com.au IN A 27.124.125.8' from ns2.crazydomains.com.au(27.124.125.3)
lookup 1stpro.info at ns2.crazydomains.com.au(27.124.125.8) 276 ms
got A record '1stpro.info IN A 43.252.138.87' from 1stpro.info(27.124.125.8)
Total time: 1198 ms