Work in progress!

Follow IntoDNS on Twitter


Category Status Test name Information
Parent Info Domain NS records Nameserver records returned by the parent servers are:

ns1.seaurchin.arvixe.com.   ['169.55.246.167'] (NO GLUE)   [TTL=86400]
ns2.seaurchin.arvixe.com.   ['108.168.166.90'] (NO GLUE)   [TTL=86400]

ns1.ns.il was kind enough to give us that information.
Warn TLD Parent Check WARNING: Looks like the parent servers do not have information for your TLD when asked. This is ok but can be confusing.
Pass Your nameservers are listed Good. The parent server ns1.ns.il has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
Info DNS Parent sent Glue The parent nameserver ns1.ns.il is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.)
Pass Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS Info NS records from your nameserversNS records got from your nameservers listed at the parent NS are:

ns1.arvixeshared.com  ['169.55.246.167']   [TTL=86400]
ns2.arvixeshared.com  ['108.168.166.90']   [TTL=86400]

Pass Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Pass Same Glue The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
Information Glue for NS records INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:
169.55.246.167
108.168.166.90
You can fix this for example by adding A records to your nameservers for the zones listed above.
Pass Mismatched NS records OK. The NS records at all your nameservers are identical.
Pass DNS servers responded Good. All nameservers listed at the parent server responded.
Pass Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.
Pass Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Pass Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Error Missing nameservers reported by parent FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
ns2.arvixeshared.com
ns1.arvixeshared.com
Error Missing nameservers reported by your nameservers ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns1.seaurchin.arvixe.com
ns2.seaurchin.arvixe.com
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
Pass Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass Different subnets OK. Looks like you have nameservers on different subnets!
Pass IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
Pass DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
Pass Different autonomous systems OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
Error Stealth NS records sent Stealth NS records were sent:
ns2.arvixeshared.com
ns1.arvixeshared.com
SOA Info SOA recordThe SOA record is:
Primary nameserver: ns1.arvixeshared.com
Hostmaster E-mail address: root.dallas151.arvixeshared.com
Serial #: 2016090123
Refresh: 3600
Retry: 7200
Expire: 1209600   2 weeks
Default TTL: 86400
Pass NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2016090123.
Warn SOA MNAME entry WARNING: SOA MNAME (ns1.arvixeshared.com) is not listed as a primary nameserver at your parent nameserver!
Pass SOA Serial Your SOA serial number is: 2016090123. This appears to be in the recommended format of YYYYMMDDnn.
Pass SOA REFRESH OK. Your SOA REFRESH interval is: 3600. That is OK
Pass SOA RETRY Your SOA RETRY value is: 7200. Looks ok
Pass SOA EXPIRE Your SOA EXPIRE number is: 1209600.Looks ok
Pass SOA MINIMUM TTL Your SOA MINIMUM TTL is: 86400. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 86400 is OK.
MX Info MX RecordsYour MX records that were reported by your nameservers are:

0   mail.2mp3.co.il   -> 2mp3.co.il->  143.95.238.10

[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
Pass Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
Pass MX name validity Good. I did not detect any invalid hostnames for your MX records.
Pass MX IPs are public OK. All of your MX records appear to use public IPs.
Warning MX CNAME Check WARNING: CNAME was returned for the following MX records:
mail.2mp3.co.il
The CNAME(s) that were returned are listed above. This is not ok per the RFCs and can cause problems including mail being lost!
Error MX A request returns CNAME WARNING: MX records points to a CNAME. CNAMEs are not allowed in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are:
mail.2mp3.co.il points to ['2mp3.co.il']
This can cause problems
Pass MX is not IP OK. All of your MX records are host names.
Info Number of MX records OK. Looks like you only have one MX record at your nameservers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
Pass Mismatched MX A OK. I did not detect differing IPs for your MX records.
Pass Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
Pass Reverse MX A records (PTR) Your reverse (PTR) record:
10.238.95.143.in-addr.arpa ->  ip-143-95-238-10.iplocal
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW Info WWW A Record Your www.2mp3.co.il A record is:
www.2mp3.co.il -> 2mp3.co.il -> [ 143.95.238.10  ]

[Looks like you have CNAME's]
Pass IPs are public OK. All of your WWW IPs appear to be public IPs.
Pass WWW CNAME OK. You do have a CNAME record for www.2mp3.co.il.Your CNAME entry also returns the A record for the CNAME entry, which is good.

Processed in 9.694 seconds.