Category

Status

Test Name

Information

Parent

PASS

Missing Direct Parent check

OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.

INFO

NS records at parent servers

Your NS records at the parent servers are:

ns1.dnslat.net. [69.93.79.50] [TTL=172800] [US]
ns2.dnslat.net. [69.93.79.51] [TTL=172800] [US]
[These were obtained from g.gtld-servers.net]

PASS

Parent nameservers have your nameservers listed

OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.

PASS

Glue at parent nameservers

OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.

NS

INFO

NS records at your nameservers

Your NS records at your nameservers are:

ns1.dnslat.net.[69.93.79.50] [TTL=14400]
ns2.dnslat.net.[69.93.79.51] [TTL=14400]

PASS

Mismatched glue

OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.

PASS

No NS A records at nameservers

OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.

PASS

All nameservers report identical NS records

OK. The NS records at all your nameservers are identical.

PASS

All nameservers respond

OK. All of your nameservers listed at the parent nameservers responded.

PASS

Nameserver name validity

OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).

PASS

Number of nameservers

OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.

PASS

Lame nameservers

OK. All the nameservers listed at the parent servers answer authoritatively for your domain.

PASS

Missing (stealth) nameservers

OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers.

PASS

Missing nameservers 2

OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.

PASS

No CNAMEs for domain

OK. There are no CNAMEs for dnslat.net. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.

PASS

No NSs with CNAMEs

OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.

WARN

Nameservers on separate class C's

WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C (technically, /24) address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.

PASS

All NS IPs public

OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.

INFO

Nameservers versions

Your nameservers have the following versions:

69.93.79.50: No version info available (timeout on lookup). Could be tinydns 1.00 through 1.04.
69.93.79.51: No version info available (timeout on lookup). Could be tinydns 1.00 through 1.04.

PASS

Stealth NS record leakage

Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.

SOA

INFO

SOA record

Your SOA record [TTL=14400] is:

Primary nameserver: ns1.dnslat.net.
Hostmaster E-mail address: soporte.americandominios.com.
Serial #: 2005032901
Refresh: 28800
Retry: 7200
Expire: 3600000
Default TTL: 86400

PASS

NS agreement on SOA serial #

OK. All your nameservers agree that your SOA serial number is 2005032901. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS Report only checks the NS records listed at the parent servers (not any stealth servers).

PASS

SOA MNAME Check

OK. Your SOA (Start of Authority) record states that your master (primary) name server is: ns1.dnslat.net.. That server is listed at the parent servers, which is correct.

PASS

SOA RNAME Check

OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: soporte@americandominios.com. (techie note: we have changed the initial '.' to an '@' for display purposes).

PASS

SOA Serial Number

OK. Your SOA serial number is: 2005032901. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.

PASS

SOA REFRESH value

OK. Your SOA REFRESH interval is : 28800 seconds. This seems normal (about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates.

PASS

SOA RETRY value

OK. Your SOA RETRY interval is : 7200 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.

WARN

SOA EXPIRE value

WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.

PASS

SOA MINIMUM TTL value

OK. Your SOA MINIMUM TTL is: 86400 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.

MX

INFO

MX Record

Your 1 MX record is:
0 dnslat.net. [TTL=14400] IP=69.93.79.50 [TTL=14400] [US]

PASS

Invalid characters

OK. All of your MX records appear to use valid hostnames, without any invalid characters.

PASS

All MX IPs public

OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.

PASS

MX records are not CNAMEs

OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.

PASS

MX A lookups have no CNAMEs

OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).

PASS

MX is host name, not IP

OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).

WARN

Multiple MX records

WARNING: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you.

PASS

Differing MX-A records

OK. I did not detect differing IPs for your MX records.

PASS

Duplicate MX records

OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.

PASS

Reverse DNS entries for MX records

OK. The IPs of all of your mail server(s) have reverse DNS (PTR) entries. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. Note that this information is cached, so if you changed it recently, it will not be reflected here (see the www.DNSstuff.com Reverse DNS Tool for the current data). The reverse DNS entries are:

50.79.93.69.in-addr.arpa 50.69-93-79.reverse.theplanet.com. [TTL=86400]

Mail

PASS

Connect to mail servers

OK: I was able to connect to all of your mailservers.