| Parent | pass | NS records at parent servers | Your NS records at the parent servers are: anycast.bit2host.eu. [ 194.0.2.13 ] anycast.bit2host.org. anycast.bit2host.co.uk. ns0.bit2host.eu. [ 66.212.249.60 ] anycast.bit2host.net. [These were obtained from nl.dns.eu.] |
| warn | Glue at parent nameservers | WARNING. The parent servers (I checked withnl.dns.eu.) 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 miliseconds in DNS. This will usually occur if your DNS servers are not in the same TLD as your domain | |
| NS | info | NS records at your nameservers | Your NS records at your nameservers are: At 194.0.2.13 At 194.0.2.13 At 194.0.2.13 At 66.212.249.60 anycast.bit2host.org. [194.0.2.13 ] ns0.bit2host.com. [66.212.249.60 ] anycast.bit2host.co.uk. [194.0.2.13 ] anycast.bit2host.com. [194.0.2.13 ] anycast.bit2host.net. [194.0.2.13 ] At 194.0.2.13 |
| skip | Mismatched glue | Skip comparing the glue provided by the parent servers and that provided by your authoritative DNS servers, as root servers do not provide glue | |
| pass | No NS A records at nameservers | OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records. | |
| fail | All nameservers report identical NS records | ERROR. The NS records at all your nameservers are different, check the info above for details. | |
| pass | All nameservers respond | OK. All of your nameservers listed at the parent nameservers responded. | |
| pass | Nameserver name validity | OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names). | |
| fail | Number of nameservers | ERROR: You have less then 2 nameservers, that may cause domain unacessible sometimes | |
| pass | Lame nameservers | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. | |
| fail | Missing (stealth) nameservers | ERROR: stealth nameservers (nameservers what does not exist at root servers , but exist at your nameservers) ns0.bit2host.com. at ns0.bit2host.eu. [66.212.249.60] anycast.bit2host.com. at ns0.bit2host.eu. [66.212.249.60] | |
| fail | Missing nameservers 2 | ERROR: missing nameservers (nameservers what exist at root servers , but does not exist at your nameservers) anycast.bit2host.eu. missing at anycast.bit2host.eu. [194.0.2.13] anycast.bit2host.org. missing at anycast.bit2host.eu. [194.0.2.13] anycast.bit2host.co.uk. missing at anycast.bit2host.eu. [194.0.2.13] ns0.bit2host.eu. missing at anycast.bit2host.eu. [194.0.2.13] anycast.bit2host.net. missing at anycast.bit2host.eu. [194.0.2.13] anycast.bit2host.eu. missing at anycast.bit2host.org. [194.0.2.13] anycast.bit2host.org. missing at anycast.bit2host.org. [194.0.2.13] anycast.bit2host.co.uk. missing at anycast.bit2host.org. [194.0.2.13] ns0.bit2host.eu. missing at anycast.bit2host.org. [194.0.2.13] anycast.bit2host.net. missing at anycast.bit2host.org. [194.0.2.13] anycast.bit2host.eu. missing at anycast.bit2host.co.uk. [194.0.2.13] anycast.bit2host.org. missing at anycast.bit2host.co.uk. [194.0.2.13] anycast.bit2host.co.uk. missing at anycast.bit2host.co.uk. [194.0.2.13] ns0.bit2host.eu. missing at anycast.bit2host.co.uk. [194.0.2.13] anycast.bit2host.net. missing at anycast.bit2host.co.uk. [194.0.2.13] anycast.bit2host.eu. missing at ns0.bit2host.eu. [66.212.249.60] ns0.bit2host.eu. missing at ns0.bit2host.eu. [66.212.249.60] anycast.bit2host.eu. missing at anycast.bit2host.net. [194.0.2.13] anycast.bit2host.org. missing at anycast.bit2host.net. [194.0.2.13] anycast.bit2host.co.uk. missing at anycast.bit2host.net. [194.0.2.13] ns0.bit2host.eu. missing at anycast.bit2host.net. [194.0.2.13] anycast.bit2host.net. missing at anycast.bit2host.net. [194.0.2.13] | |
| pass | Nameservers on separate class C's | Your nameservers seems to be in different networks. | |
| pass | All NS IPs public | OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays. | |
| SOA | info | SOA record | Your SOA record is: At anycast.bit2host.eu.[194.0.2.13] Primary nameserver: Hostmaster E-mail address: Serial #: Refresh: Retry: Expire: Default TTL: At anycast.bit2host.org.[194.0.2.13] Primary nameserver: Hostmaster E-mail address: Serial #: Refresh: Retry: Expire: Default TTL: At anycast.bit2host.co.uk.[194.0.2.13] Primary nameserver: Hostmaster E-mail address: Serial #: Refresh: Retry: Expire: Default TTL: At ns0.bit2host.eu.[66.212.249.60] Primary nameserver: ns0.bit2host.com. Hostmaster E-mail address: dnsadmin.bit2host.com. Serial #: 2013052101 Refresh: 3600 Retry: 1200 Expire: 2592000 Default TTL:60 At anycast.bit2host.net.[194.0.2.13] Primary nameserver: Hostmaster E-mail address: Serial #: Refresh: Retry: Expire: Default TTL: |
| fail | NS agreement on SOA Serial # | ERROR: some nameservers have different soa serial number, that can occur because recent master update (slave have not loaded master zone yet) or probably the is a problem in DNS. | |
| fail | SOA MNAME Check | ERROR: Your SOA (Start of Authority) record states that your master (primary) name server is: That server is not listed at the parent servers, which is not correct. | |
| warn | SOA Serial Number | Your SOA serial number is: . This not 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. | |
| warn | SOA REFRESH value | Your SOA REFRESH interval is : seconds. This seems too small (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. | |
| warn | SOA RETRY value | Your SOA RETRY interval is : seconds. This seems too small (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. | |
| warn | SOA EXPIRE value | Your SOA EXPIRE time is : seconds. This seems too small (about 1209600 to 2419200 seconds (2-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. | |
| warn | SOA MINIMUM TTL value | Your SOA MINIMUM TTL is : seconds. This seems too small (about 3,600 to 86400 seconds or 1-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. | |