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 wolkartweb.pro
==============

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

ns3.mchost.ru. [NO GLUE] [TTL=86400]
ns2.mchost.ru. [NO GLUE] [TTL=86400]
ns4.mchost.ru. [NO GLUE] [TTL=86400]
ns1.mchost.ru. [NO GLUE] [TTL=86400]

This information was kindly provided by a0.pro.afilias-nst.info.
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!
INFOParent servers return glueOK. The TLD of your domain (pro) differs from that of your nameservers (ru). As such, the parent servers are not required to send glue.
INFOA record for each NS at parentOK. The parent servers don't need to have A records for your nameservers since the TLD of your domain (pro) differs from that of your nameservers (ru).

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

ns1.mchost.ru. [NO GLUE] [TTL=600]
ns2.mchost.ru. [NO GLUE] [TTL=600]
ns3.mchost.ru. [NO GLUE] [TTL=600]
ns4.mchost.ru. [NO GLUE] [TTL=600]
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 serversOK. Since the GTLD for your domain (pro) differs from that of your nameservers (ru), the result of this test are irrelevant since the parent servers aren't even required to hold the A records for your nameservers.
FAILEDSame NS records at each local nameserverOops! Your name servers don't all seem to have identical NS records for your domain. This could lead to some visitors not being able to see your site (or seeing it on a different server)! This should be fixed ASAP!
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 'wolkartweb.pro'. 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.
FAILEDNo CNAME records for nameserversOops! One or more 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 are present for a nameserver. This is due to the fact that having a CNAME (essentially a redirect) and any other record (explicit values) will cause confusion over which takes priority.
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: ns1.mchost.ru.
Hostmaster E-mail address: info.mchost.ru.
Serial number: 1560694332
Refresh: 28800
Retry: 7200
Expire: 604800
Minimum TTL: 600
PASSEDAll nameservers have same SOA serial numberGood! All your nameservers agree that your SOA serial number is 1560694332
PASSEDSOA primary nameserver listed at parentGood! The primary nameserver listed in your SOA record (ns1.mchost.ru.) is listed at the parent servers!
WARNINGSOA serial number formatOops! Your SOA serial number (1560694332) 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 (28800) is within the recommended range of 1 hour (3600) to 1 day (86400).
PASSEDSOA Retry valueGood! Your SOA Retry value (7200) is within the recommended range of 5 minutes (300) to 4 hours (14400).
PASSEDSOA Expire valueGood! Your SOA Expire value (604800) is within the recommended range of 1 week (604800) to 4 weeks (2419200).
PASSEDSOA Minimum TTL valueGood! Your SOA Minimum TTL value (600) 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 mx.yandex.net. [TTL=600]
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.
WARNINGNumber of MX recordsOops! You only have one MX record! In the event that this mail server is down, you could potentially lose mail! It is recommended to have two or more MX records (and hence mail servers) if you want uninterrupted mail functionality.
PASSEDDuplicate MX A recordsGood! No two MX records resolve to the same IP address.
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:

89.134.158.93.in-addr.arpa <--> mx.yandex.ru.

WWW Record Tests
StatusTest CaseInformation
INFOWWW recordwww.wolkartweb.pro A records are:

www.wolkartweb.pro. CNAME wolkartweb.pro. [TTL=600]
wolkartweb.pro. A 178.208.83.42 [TTL=600]
PASSEDWWW A record has public IPGood! The IP address(es) of the A records returned for your WWW record have public IP addresses.
PASSEDWWW CNAME lookupGood! You have a CNAME entry for your WWW record which also returns the associated A record! This saves an extra lookup which would delay loading times for your site.




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