|NS records listed at parent servers||Nameserver records returned by the parent servers are:|
ns.exohosting.sk. [220.127.116.11] [TTL=3600]
ns1.exohosting.eu. [NO GLUE] [TTL=3600]
ns3.exohosting.cz. [NO GLUE] [TTL=3600]
This information was kindly provided by h.tld.sk.
|Domain listed at parent servers||Good! The parent servers have information on your domain. Some other domains (like .co.us) do not have a DNS zone at the parent servers.|
|NS records listed at parent servers||Good! The parent servers have your NS records listed. If they didn't, people wouldn't be able to find your domain!|
|Parent servers return glue||Good! The TLD of your domain (sk) matches the TLD of your nameservers (sk) and hence the parent servers MUST return the IP (glue) for your NS records... AND THEY DO!|
|A record for each NS at parent||Oops! The parent servers don't have A records for each of your nameservers! This isn't a fatal error but means an extra lookup needs to be performed increasing the load time to your site.|
|NS records at your local servers||NS records retrieved from your local nameservers were:|
ns.exohosting.sk. [NO GLUE] [TTL=3600]
ns1.exohosting.sk. [NO GLUE] [TTL=3600]
ns3.exohosting.sk. [NO GLUE] [TTL=3600]
|Glue at local nameservers||Oops! Your local nameservers don't return IP addresses (glue) along with your NS records! This isn't a fatal error but means an extra lookup needs to be performed increasing the load time to your site. You can fix this by adding A records for each of the nameservers listed above.|
|Same glue at local and parent servers||Hrmm. Either the parent servers or your servers aren't returning GLUE for your nameservers. This means an extra lookup needs to be performed to get the IP's of your nameservers.|
|Same NS records at each local nameserver||Good! All your local nameservers have identical NS records for your domain.|
|Check that all nameservers respond||Good! All of your nameservers listed at the parent servers responded.|
|Check all nameservers are valid||Good! All of your nameservers appear to be valid (e.g. are not IP addresses or partial domain names)|
|Number of nameservers||Good! You have at least 2 nameservers. Whilst RFC218 section 2.5 specifies a minimum of 3, as long as you have 2 or more, you should be ok!|
|Local nameservers answer authoritatively||Good! All your nameservers answer authoritatively for your domain.|
|Missing NS records at parent servers||Oops! It appears that the following nameserves listed at your local servers are not listed at the parent servers:|
You should ensure that these nameservers are valid and working. If they are not, you will encounter connectivity issues with your domain.
|Missing NS records at local servers||Oops! It appears that the following nameserves listed at the parent servers are not listed at your local servers:|
You should ensure that these nameservers are valid and working. If they aren't, it can cause odd behaviour including some people not being able to access your domain.
|No CNAME records for domain||Good! No CNAME records are present for 'excellence.sk'. RFC1912 section 2.4 and RFC2181 section 10.3 state that there should be no CNAME records if any other records are present for a given domain.|
|No CNAME records for nameservers||Good! No CNAME records are present for your nameservers. RFC1912 section 2.4 and RFC2181 section 10.3 state that there should be no CNAME records if any other records (e.g. an A record) are present for a nameserver.|
|Nameservers are on different IP subnets||Good! All your nameservers are in separate class C (/24) subnets.|
|Nameservers have public IP's||Good! All your NS records have public IP addresses.|
|Nameservers allow TCP connections||Good! We can establish a TCP connection with each of your nameservers on port 53. Whilst UDP is most commonly used for the DNS protocol, TCP connections are occasionally used.|
|SOA Record||Your Start of Authority (SOA) record is:|
Primary nameserver: ns.excellence.sk.
Hostmaster E-mail address: ns.excellence.sk.
Serial number: 2014020416
Minimum TTL: 3600
|All nameservers have same SOA serial number||Good! All your nameservers agree that your SOA serial number is 2014020416|
|SOA primary nameserver listed at parent||Oops! The primary nameserver listed in your SOA record (ns.excellence.sk.) is not listed at the parent servers! This could suggest a configuration issue with your SOA record.|
|SOA serial number format||Good! Your SOA serial number (2014020416) appears to be in the recommended format (YYYYMMDDnn - where nn is the revision number).|
|SOA Refresh value||Good! Your SOA Refresh value (10800) is within the recommended range of 1 hour (3600) to 1 day (86400).|
|SOA Retry value||Good! Your SOA Retry value (1800) is within the recommended range of 5 minutes (300) to 4 hours (14400).|
|SOA Expire value||Good! Your SOA Expire value (604800) is within the recommended range of 1 week (604800) to 4 weeks (2419200).|
|SOA Minimum TTL value||Good! Your SOA Minimum TTL value (3600) is within the recommended range of less than 3 days (259200).|
|MX Records||Your Mail eXchanger (MX) records are: |
10 relay.exohosting.sk. [TTL=3600]
10 relay1.exohosting.sk. [TTL=3600]
15 relay3.dnsserver.eu. [TTL=3600]
20 relay2.dnsserver.eu. [TTL=3600]
|All nameservers have same MX records||Good! All of your nameservers have the same MX records.|
|All MX records contain valid hostnames||Good! All of your MX entries have valid hostnames (e.g. are not IP's or invalid domain names).|
|All MX records use public IP addresses||Good! All of your MX entries have public IP addresses.|
|MX record is not a CNAME/alias||Good! When querying for your MX records we did not receive a CNAME record as a result.|
|MX A records are not CNAME's||Good! No CNAME records are present for your MX A records.|
|Number of MX records||Good! You have more than one MX record. In the event that the primary mail server is down, you have at least one backup that will continue to accept mail!|
|Duplicate MX A records||Oops! The IP address of one or more of your MX records is the same as another MX record. This means that the duplicate servers are not providing any redundancy at all!|
|Differing MX A records||Good! You have no different IP's for your MX A records than the DNS server that is authoritive for that hostname.|
|MX records have reverse DNS entries||Good! All your MX IP addresses have reverse DNS entries. The reverse entries returned were:|
18.104.22.168.in-addr.arpa <--> relay3s80.dnsserver.eu.
22.214.171.124.in-addr.arpa <--> relay3s88.dnsserver.eu.
126.96.36.199.in-addr.arpa <--> relay3s116.dnsserver.eu.
188.8.131.52.in-addr.arpa <--> relay3s116.dnsserver.eu.