ns.planethoster.net DNS Report

Health Score: 84%

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

Checked: 8 months before

Parent

NS records at parent servers

nsb.planethoster.net [ 85.236.159.10 ]
nsc.planethoster.net [ 185.22.111.10 ]
nsa.planethoster.net [ 199.188.223.10 ]
[These were obtained from anycast1.planethoster.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.
(nsa.planethoster.net.	14400	IN	A	199.188.223.10) present at Parent, missing at (85.236.159.10, 185.22.111.10, 199.188.223.10)
(nsb.planethoster.net.	14400	IN	A	85.236.159.10) present at Parent, missing at (85.236.159.10, 185.22.111.10, 199.188.223.10)
(nsc.planethoster.net.	14400	IN	A	185.22.111.10) present at Parent, missing at (85.236.159.10, 185.22.111.10, 199.188.223.10)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (nsc.planethoster.net,nsb.planethoster.net,nsa.planethoster.net) at nameserver 85.236.159.10
missing A record(s) for (nsb.planethoster.net,nsc.planethoster.net,nsa.planethoster.net) at nameserver 185.22.111.10
missing A record(s) for (nsc.planethoster.net,nsb.planethoster.net,nsa.planethoster.net) at nameserver 199.188.223.10

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 3 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
support.planethoster.info
Serial
2020012603
Refresh
86400
Retry
7200
Expire
3600000
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2020012603 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: nsa.planethoster.net That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2020012603 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 ns.planethoster.net
lookup ns.planethoster.net at A.ROOT-SERVERS.NET(198.41.0.4) 43 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns.planethoster.net at a.gtld-servers.net(192.5.6.30) 42 ms
a.gtld-servers.net(192.5.6.30) refer to anycast1.planethoster.net(199.188.223.20)
lookup ns.planethoster.net at anycast1.planethoster.net(199.188.223.20) 79 ms
anycast1.planethoster.net(199.188.223.20) refer to nsb.planethoster.net(85.236.159.10)
lookup ns.planethoster.net at nsb.planethoster.net(85.236.159.10) 78 ms
got A record 'ns.planethoster.net IN A 185.22.111.20' from ns.planethoster.net(85.236.159.10)
Total time: 242 ms