dnn-services.nl DNS Report

Health Score: 86%

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

Checked: 1 week before

Parent

NS records at parent servers

ns0.transip.net
ns1.transip.net
ns2.transip.net
[These were obtained from ns3.dns.nl.]

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 transip.net

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.transip.net,ns0.transip.net,ns2.transip.net) at nameserver 80.69.67.67
missing A record(s) for (ns2.transip.net,ns0.transip.net,ns1.transip.net) at nameserver 80.69.69.69
missing A record(s) for (ns2.transip.net,ns0.transip.net,ns1.transip.net) at nameserver 37.97.255.53

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
hostmaster.transip.nl
Serial
2017121803
Refresh
14400
Retry
1800
Expire
2419200
TTL
3600

Serial agreement 7/7

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

Serial value 1/1

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

SUCCESS SOA Retry interval is : 1800 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 1/1

SUCCESS SOA Expire time is : 2419200 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 : 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 dnn-services.nl
lookup dnn-services.nl at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns3.dns.nl(194.171.17.10)
lookup dnn-services.nl at ns3.dns.nl(194.171.17.10) 91 ms
ns3.dns.nl(194.171.17.10) refer to ns1.transip.net(unknow IP)
extra IP lookup for ns1.transip.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.transip.net 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 ns1.transip.net at a.gtld-servers.net(192.5.6.30) 12 ms
a.gtld-servers.net(192.5.6.30) refer to ns0.transip.net(80.69.67.67)
lookup ns1.transip.net at ns0.transip.net(80.69.67.67) 93 ms
got A record 'ns1.transip.net IN A 80.69.69.69' from ns1.transip.net(80.69.67.67)
lookup dnn-services.nl at ns1.transip.net(80.69.69.69) 82 ms
got A record 'dnn-services.nl IN A 84.241.134.130' from dnn-services.nl(80.69.69.69)
Total time: 302 ms