ViewDNS.info - Your one source for DNS related tools!
ViewDNS.info > Tools >

DNS Report



View a complete report on the DNS settings for your domain. This tool is designed to assist webmasters and system administrators diagnose DNS related issues. A number of tests are run on your DNS settings with results displayed in an easy to understand manner.

Domain (e.g. domain.com):

DNS Report for pingloans.co.uk
==============

Parent Nameserver Tests
StatusTest CaseInformation
INFONS records listed at parent serversNameserver records returned by the parent servers are:

ns2.heyrank.co.uk. [195.154.179.176] [TTL=172800]
ns1.heyrank.co.uk. [195.154.179.176] [TTL=172800]

This information was kindly provided by nsd.nic.uk.
PASSEDDomain listed at parent serversGood! The parent servers have information on your domain. Some other domains (like .co.us) do not have a DNS zone at the parent servers.
PASSEDNS records listed at parent serversGood! The parent servers have your NS records listed. If they didn't, people wouldn't be able to find your domain!
PASSEDParent servers return glueGood! The TLD of your domain (uk) matches the TLD of your nameservers (uk) and hence the parent servers MUST return the IP (glue) for your NS records... AND THEY DO!
PASSEDA record for each NS at parentGood! The parent servers have A records for each of your nameservers.

Local Nameserver Tests
StatusTest CaseInformation
INFONS records at your local serversNS records retrieved from your local nameservers were:

WARNINGGlue at local nameserversOops! 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.
INFOSame glue at local and parent serversHrmm. 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.
PASSEDSame NS records at each local nameserverGood! All your local nameservers have identical NS records for your domain.
FAILEDCheck that all nameservers respondOops! The following nameservers listed at the parent servers didn't respond to DNS requests:

ns2.heyrank.co.uk.
ns1.heyrank.co.uk.

This means that some people won't be able to view your site! It also means some of the tests below which check for the same results across all your local nameservers will fail.
PASSEDCheck all nameservers are validGood! All of your nameservers appear to be valid (e.g. are not IP addresses or partial domain names)
PASSEDNumber of nameserversGood! 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!
FAILEDLocal nameservers answer authoritativelyOops! The following nameservers do not answer authoritatively for your domain:

ns2.heyrank.co.uk.
ns1.heyrank.co.uk.

This means that these servers don't have a zone file for your domain and are simply looking up the details themselves! This is not a good thing!
PASSEDMissing NS records at parent serversGood! The parent servers have all the nameservers listed for your domain as your local nameservers!
FAILEDMissing NS records at local serversOops! It appears that the following nameserves listed at the parent servers are not listed at your local servers:

ns1.heyrank.co.uk.
ns2.heyrank.co.uk.

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.
PASSEDNo CNAME records for domainGood! No CNAME records are present for 'pingloans.co.uk'. 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.
PASSEDNo CNAME records for nameserversGood! 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.
WARNINGNameservers are on different IP subnetsOops! One or more of your nameservers are on the same class C subnet. RFC2182 section 3.1 states that all of your nameservers should be in geographically and topologically dispersed locations for redundancy purposes.
PASSEDNameservers have public IP'sGood! All your NS records have public IP addresses.
PASSEDNameservers allow TCP connectionsGood! 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.

Start of Authority (SOA) Tests
StatusTest CaseInformation
INFOSOA RecordYour Start of Authority (SOA) record is:

Primary nameserver:
Hostmaster E-mail address:
Serial number:
Refresh:
Retry:
Expire:
Minimum TTL:
PASSEDAll nameservers have same SOA serial numberGood! All your nameservers agree that your SOA serial number is
WARNINGSOA primary nameserver listed at parentOops! The primary nameserver listed in your SOA record () is not listed at the parent servers! This could suggest a configuration issue with your SOA record.
WARNINGSOA serial number formatOops! Your SOA serial number () doesn't seem to be in the recommended format (YYYYMMDDnn - where nn is the revision number). This is still OK, however as long as you are keeping track of your SOA version details.
WARNINGSOA Refresh valueOops! Your SOA Refresh value () is outside of the recommended range of 1 hour (3600) to 1 day (86400). This value basically means 'how long can the secondary nameserver have out of date information after updating the primary nameserver?' and should be within the recommended range.
WARNINGSOA Retry valueOops! Your SOA Retry value () is outside of the recommended range of 1 hour (3600) to 4 hours (14400). This value determines how long your nameservers will wait to retry after a failed refresh attempt. If the value is too low (<3600) chances are it will fail over and over causing extra traffic use and load on the nameserver, if it is too high (>14400) you will have out of date information on one of your nameservers for longer than necessary.
WARNINGSOA Expire valueOops! Your SOA Expire value () is outside of the recommended range of 1 week (604800) to 4 weeks (2419200). This value determines how long a secondary server may keep information before it is no longer authoritive. If this value is too low, the secondary servers may stop responding authoritatively too soon in the event of an outage on the primary nameserver. If it is too high, it may answer authortively for too long if it cannot reach the primary nameserver due network issues (e.g. firewall) making diagnosis difficult.
PASSEDSOA Minimum TTL valueGood! Your SOA Minimum TTL value () is within the recommended range of less than 3 days (259200).

Mail eXchanger (MX) Tests
StatusTest CaseInformation
FAILEDMX RecordsYou don't appear to have any Mail eXchanger (MX) records for your domain. This means you will not be able to receive email at this domain name (e.g. yourname@pingloans.co.uk). If you wish to use mail on this domain, you should configure one or more MX records.

WWW Record Tests
StatusTest CaseInformation
INFOWWW recordwww.pingloans.co.uk A records are:

PASSEDWWW A record has public IPGood! The IP address(es) of the A records returned for your WWW record have public IP addresses.
FAILEDWWW CNAME lookupOops! You don't have a CNAME entry or an A record for your WWW record. This means that no-one will see your site when they visit www.pingloans.co.uk!




All content © 2018 ViewDNS.info
Feedback / Suggestions / Contact Us   Become an Affiliate