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 cnn.com
==============

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

ns-47.awsdns-05.com. [205.251.192.47] [TTL=172800]
ns-576.awsdns-08.net. [205.251.194.64] [TTL=172800]
ns-1630.awsdns-11.co.uk. [NO GLUE] [TTL=172800]
ns-1086.awsdns-07.org. [NO GLUE] [TTL=172800]

This information was kindly provided by l.gtld-servers.net.
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 (com) matches the TLD of your nameservers (com) and hence the parent servers MUST return the IP (glue) for your NS records... AND THEY DO!
WARNINGA record for each NS at parentOops! 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.

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

ns-1086.awsdns-07.org. [NO GLUE] [TTL=3600]
ns-1630.awsdns-11.co.uk. [NO GLUE] [TTL=3600]
ns-47.awsdns-05.com. [NO GLUE] [TTL=3600]
ns-576.awsdns-08.net. [NO GLUE] [TTL=3600]
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.
PASSEDCheck that all nameservers respondGood! All of your nameservers listed at the parent servers responded.
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!
PASSEDLocal nameservers answer authoritativelyGood! All your nameservers answer authoritatively for your domain.
PASSEDMissing NS records at parent serversGood! The parent servers have all the nameservers listed for your domain as your local nameservers!
PASSEDMissing NS records at local serversGood! Your local servers have all the nameservers listed for your domain that are listed at the parent servers!
PASSEDNo CNAME records for domainGood! No CNAME records are present for 'cnn.com'. 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.
PASSEDNameservers are on different IP subnetsGood! All your nameservers are in separate class C (/24) subnets.
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: ns-47.awsdns-05.com.
Hostmaster E-mail address: awsdns-hostmaster.amazon.com.
Serial number: 1
Refresh: 7200
Retry: 900
Expire: 1209600
Minimum TTL: 86400
PASSEDAll nameservers have same SOA serial numberGood! All your nameservers agree that your SOA serial number is 1
PASSEDSOA primary nameserver listed at parentGood! The primary nameserver listed in your SOA record (ns-47.awsdns-05.com.) is listed at the parent servers!
WARNINGSOA serial number formatOops! Your SOA serial number (1) 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.
PASSEDSOA Refresh valueGood! Your SOA Refresh value (7200) is within the recommended range of 1 hour (3600) to 1 day (86400).
PASSEDSOA Retry valueGood! Your SOA Retry value (900) is within the recommended range of 5 minutes (300) to 4 hours (14400).
PASSEDSOA Expire valueGood! Your SOA Expire value (1209600) is within the recommended range of 1 week (604800) to 4 weeks (2419200).
PASSEDSOA Minimum TTL valueGood! Your SOA Minimum TTL value (86400) is within the recommended range of less than 3 days (259200).

Mail eXchanger (MX) Tests
StatusTest CaseInformation
INFOMX RecordsYour Mail eXchanger (MX) records are:

10 mxa-000c6b02.gslb.pphosted.com. [TTL=300]
10 mxb-000c6b02.gslb.pphosted.com. [TTL=300]
PASSEDAll nameservers have same MX recordsGood! All of your nameservers have the same MX records.
PASSEDAll MX records contain valid hostnamesGood! All of your MX entries have valid hostnames (e.g. are not IP's or invalid domain names).
PASSEDAll MX records use public IP addressesGood! All of your MX entries have public IP addresses.
PASSEDMX record is not a CNAME/aliasGood! When querying for your MX records we did not receive a CNAME record as a result.
PASSEDMX A records are not CNAME'sGood! No CNAME records are present for your MX A records.
PASSEDNumber of MX recordsGood! 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!
WARNINGDuplicate MX A recordsOops! 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!
PASSEDDiffering MX A recordsGood! You have no different IP's for your MX A records than the DNS server that is authoritive for that hostname.
PASSEDMX records have reverse DNS entriesGood! All your MX IP addresses have reverse DNS entries. The reverse entries returned were:

47.153.163.148.in-addr.arpa <--> mx0b-000c6b02.pphosted.com.
47.153.163.148.in-addr.arpa <--> mx0b-000c6b02.pphosted.com.

WWW Record Tests
StatusTest CaseInformation
INFOWWW recordwww.cnn.com A records are:

www.cnn.com. CNAME turner-tls.map.fastly.net. [TTL=300]
PASSEDWWW A record has public IPGood! The IP address(es) of the A records returned for your WWW record have public IP addresses.
WARNINGWWW CNAME lookupOops! You have a CNAME entry for your WWW record but the A record associated is not returned with it! This means an extra lookup needs to be performed, unecessarily increasing loading times for your site.




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