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:

ns5.ev1servers.net.   ['207.218.247.135']   [TTL=172800]
ns6.ev1servers.net.   ['207.218.223.162']   [TTL=172800]
ns10.dnsmadeeasy.com.   ['208.94.148.4']   [TTL=172800]
ns11.dnsmadeeasy.com.   ['208.80.124.4']   [TTL=172800]
ns12.dnsmadeeasy.com.   ['208.80.126.4']   [TTL=172800]
ns13.dnsmadeeasy.com.   ['208.80.125.4']   [TTL=172800]
ns14.dnsmadeeasy.com.   ['208.80.127.4']   [TTL=172800]
ns15.dnsmadeeasy.com.   ['208.94.149.4']   [TTL=172800]

j.gtld-servers.net was kind enough to give us that information.
Pass TLD Parent Check Good. j.gtld-servers.net, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
Pass Your nameservers are listed Good. The parent server j.gtld-servers.net 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.
Pass DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
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:

ns13.dnsmadeeasy.com  ['208.80.125.4']   [TTL=86400]
ns11.dnsmadeeasy.com  ['208.80.124.4']   [TTL=86400]
ns10.dnsmadeeasy.com  ['208.94.148.4']   [TTL=86400]
ns12.dnsmadeeasy.com  ['208.80.126.4']   [TTL=86400]
ns15.dnsmadeeasy.com  ['208.94.149.4']   [TTL=86400]
ns14.dnsmadeeasy.com  ['208.80.127.4']   [TTL=86400]
ns1.theplanet.com  ['207.218.247.135']   [TTL=86400]
ns2.theplanet.com  ['207.218.223.162']   [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:
208.94.149.4
208.94.148.4
208.80.126.4
208.80.124.4
208.80.127.4
208.80.125.4
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.theplanet.com
ns1.theplanet.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:
ns6.ev1servers.net
ns5.ev1servers.net
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.
Pass Stealth NS records sent Ok. No stealth ns records are sent
SOA Info SOA recordThe SOA record is:
Primary nameserver: ns10.dnsmadeeasy.com
Hostmaster E-mail address: dns.dnsmadeeasy.com
Serial #: 2009010115
Refresh: 43200
Retry: 3600
Expire: 1209600   2 weeks
Default TTL: 180
Error NSs have same SOA serial Looks like your nameservers do not agree on the SOA serial. Ths SOA records as reported by your nameservers:
208.94.149.4 ->  2009010115
208.80.124.4 ->  2009010115
208.94.148.4 ->  2009010115
208.80.126.4 ->  2009010115
207.218.223.162 ->  2011081801
208.80.127.4 ->  2009010115
207.218.247.135 ->  2011081801
208.80.125.4 ->  2009010115
This can cause some serious problems that is why you should fix this asap.
Pass SOA MNAME entry OK. ns10.dnsmadeeasy.com That server is listed at the parent servers.
Pass SOA Serial Your SOA serial number is: 2009010115. This appears to be in the recommended format of YYYYMMDDnn.
Pass SOA REFRESH OK. Your SOA REFRESH interval is: 43200. That is OK
Pass SOA RETRY Your SOA RETRY value is: 3600. Looks ok
Pass SOA EXPIRE Your SOA EXPIRE number is: 1209600.Looks ok
Pass SOA MINIMUM TTL Your SOA MINIMUM TTL is: 180. 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 180 is OK.
MX Info MX RecordsYour MX records that were reported by your nameservers are:

10   mail.mmjrevu.com   74.55.59.59
10   aspmx.l.google.com   173.194.65.27 (no glue)
20   alt1.aspmx.l.google.com   74.125.130.27 (no glue)
30   alt2.aspmx.l.google.com   74.125.23.27 (no glue)
40   aspmx2.googlemail.com   74.125.200.27 (no glue)
50   aspmx3.googlemail.com   74.125.204.27 (no glue)

[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. ]
Warning Different MX records at nameservers The MX records that are not the same at all your nameservers:
mail.mmjrevu.com with ip(s): 74.55.59.59  reported only by: 208.94.149.4 208.94.148.4 208.80.124.4 208.80.125.4 208.80.126.4 208.80.127.4
aspmx.l.google.com with ip(s): 173.194.65.27  reported only by: 207.218.223.162 207.218.247.135
alt1.aspmx.l.google.com with ip(s): 74.125.130.27  reported only by: 207.218.223.162 207.218.247.135
alt2.aspmx.l.google.com with ip(s): 74.125.23.27  reported only by: 207.218.223.162 207.218.247.135
aspmx2.googlemail.com with ip(s): 74.125.200.27  reported only by: 207.218.223.162 207.218.247.135
aspmx3.googlemail.com with ip(s): 74.125.204.27  reported only by: 207.218.223.162 207.218.247.135
It is better to have the same MX records at all your nameservers!
Pass MX name validity Good. I did not detect any invalid hostnames for your MX records.
Error MX IPs are public The MX ips that do not seem valid:
127.0.0.1
This can cause problems
Pass MX CNAME Check OK. No problems here.
Pass MX A request returns CNAME OK. No CNAMEs returned for A records lookups.
Pass MX is not IP OK. All of your MX records are host names.
Pass Number of MX records OK. Looks like you have multiple MX records. However none of your MX record is common at all your nameservers meaning every nameserver has different sets of MX records. This seems bad but if you know what are you doing it's ok.
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.
Error Reverse MX A records (PTR) ERROR: No reverse DNS (PTR) entries. The problem MX records are:
27.204.125.74.in-addr.arpa -> no reverse (PTR) detected
27.130.125.74.in-addr.arpa -> no reverse (PTR) detected
You should contact your ISP and ask him to add a PTR record for your ips
WWW Info WWW A Record Your www.mmjrevu.com A record is:
www.mmjrevu.com  [184.73.161.98] 
Pass IPs are public OK. All of your WWW IPs appear to be public IPs.
Pass WWW CNAME OK. No CNAME

Processed in 0.995 seconds.