fc-borussia-brandenburg.de DNS Report

Health Score: 86%

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

Checked: 1 month before

Parent

NS records at parent servers 

ns1060.ui-dns.biz
ns1060.ui-dns.org
ns1060.ui-dns.com
ns1060.ui-dns.de
[These were obtained from a.nic.de.]

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 ui-dns.biz Check ui-dns.org Check ui-dns.com Check ui-dns.de

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (ns1060.ui-dns.com,ns1060.ui-dns.biz,ns1060.ui-dns.org,ns1060.ui-dns.de) at nameserver 217.160.81.60
missing A record(s) for (ns1060.ui-dns.de,ns1060.ui-dns.com,ns1060.ui-dns.biz,ns1060.ui-dns.org) at nameserver 217.160.83.60
missing A record(s) for (ns1060.ui-dns.org,ns1060.ui-dns.de,ns1060.ui-dns.com,ns1060.ui-dns.biz) at nameserver 217.160.82.60
missing A record(s) for (ns1060.ui-dns.com,ns1060.ui-dns.de,ns1060.ui-dns.biz,ns1060.ui-dns.org) at nameserver 217.160.80.60

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 4 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.1und1.de
Serial
2017051603
Refresh
28800
Retry
7200
Expire
604800
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2017051603 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: ns1060.ui-dns.org That server is listed at the parent servers, which is correct.

Serial value 1/1

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

SUCCESS SOA Expire time is : 604800 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 fc-borussia-brandenburg.de
lookup fc-borussia-brandenburg.de at A.ROOT-SERVERS.NET(198.41.0.4) 7 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.de(194.0.0.53)
lookup fc-borussia-brandenburg.de at a.nic.de(194.0.0.53) 11 ms
a.nic.de(194.0.0.53) refer to ns1060.ui-dns.biz(unknow IP)
extra IP lookup for ns1060.ui-dns.biz at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1060.ui-dns.biz at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to k.gtld.biz(156.154.128.65)
lookup ns1060.ui-dns.biz at k.gtld.biz(156.154.128.65) 11 ms
k.gtld.biz(156.154.128.65) refer to ns-biz.ui-dns.biz(217.160.81.195)
lookup ns1060.ui-dns.biz at ns-biz.ui-dns.biz(217.160.81.195) 3 ms
got A record 'ns1060.ui-dns.biz IN A 217.160.81.60' from ns1060.ui-dns.biz(217.160.81.195)
lookup fc-borussia-brandenburg.de at ns1060.ui-dns.biz(217.160.81.60) 3 ms
got A record 'fc-borussia-brandenburg.de IN A 217.160.0.53' from fc-borussia-brandenburg.de(217.160.81.60)
Total time: 40 ms