|NS records listed at parent servers||Nameserver records returned by the parent servers are:|
dns.sea1.nytimes.com. [22.214.171.124] [TTL=172800]
dns.ewr1.nytimes.com. [126.96.36.199] [TTL=172800]
This information was kindly provided by m.gtld-servers.net.
|Domain listed at parent servers||Good! The parent servers have information on your domain. Some other domains (like .co.us) do not have a DNS zone at the parent servers.|
|NS records listed at parent servers||Good! The parent servers have your NS records listed. If they didn't, people wouldn't be able to find your domain!|
|Parent servers return glue||Good! 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!|
|A record for each NS at parent||Good! The parent servers have A records for each of your nameservers.|
|NS records at your local servers||NS records retrieved from your local nameservers were:|
dns.ewr1.nytimes.com. [188.8.131.52] [TTL=300]
dns.sea1.nytimes.com. [184.108.40.206] [TTL=300]
|Glue at local nameservers||Good! Your local nameservers send the IP address (glue) along with your NS records.|
|Same glue at local and parent servers||Good! Both the parent servers and your local servers report the same IP addresses (GLUE) for your nameservers!|
|Same NS records at each local nameserver||Good! All your local nameservers have identical NS records for your domain.|
|Check that all nameservers respond||Good! All of your nameservers listed at the parent servers responded.|
|Check all nameservers are valid||Good! All of your nameservers appear to be valid (e.g. are not IP addresses or partial domain names)|
|Number of nameservers||Good! 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!|
|Local nameservers answer authoritively||Good! All your nameservers answer authoritatively for your domain.|
|Missing NS records at parent servers||Good! The parent servers have all the nameservers listed for your domain as your local nameservers!|
|Missing NS records at local servers||Good! Your local servers have all the nameservers listed for your domain that are listed at the parent servers!|
|No CNAME records for domain||Good! No CNAME records are present for 'nytimes.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.|
|No CNAME records for nameservers||Good! 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.|
|Nameservers are on different IP subnets||Good! All your nameservers are in separate class C (/24) subnets.|
|Nameservers have public IP's||Good! All your NS records have public IP addresses.|
|Nameservers allow TCP connections||Good! 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.|
|SOA Record||Your Start of Authority (SOA) record is:|
Primary nameserver: dns.sea1.nytimes.com.
Hostmaster E-mail address: hostmaster.nytimes.com.
Serial number: 2013062467
Minimum TTL: 300
|All nameservers have same SOA serial number||Good! All your nameservers agree that your SOA serial number is 2013062467|
|SOA primary nameserver listed at parent||Good! The primary nameserver listed in your SOA record (dns.sea1.nytimes.com.) is listed at the parent servers!|
|SOA serial number format||Good! Your SOA serial number (2013062467) appears to be in the recommended format (YYYYMMDDnn - where nn is the revision number).|
|SOA Refresh value||Oops! Your SOA Refresh value (300) is outside of the recommended range of 1 hour (3600) to 1 day (86400). This value basically means 'how long can the secondary nameserver have out of date information after updating the primary nameserver?' and should be within the recommended range.|
|SOA Retry value||Oops! Your SOA Retry value (150) is outside of the recommended range of 1 hour (3600) to 4 hours (14400). This value determines how long your nameservers will wait to retry after a failed refresh attempt. If the value is too low (<3600) chances are it will fail over and over causing extra traffic use and load on the nameserver, if it is too high (>14400) you will have out of date information on one of your nameservers for longer than necessary.|
|SOA Expire value||Good! Your SOA Expire value (1209600) is within the recommended range of 1 week (604800) to 4 weeks (2419200).|
|SOA Minimum TTL value||Good! Your SOA Minimum TTL value (300) is within the recommended range of less than 3 days (259200).|
|MX Records||Your Mail eXchanger (MX) records are: |
1 ASPMX.L.GOOGLE.com. [TTL=300]
5 ALT1.ASPMX.L.GOOGLE.com. [TTL=300]
5 ALT2.ASPMX.L.GOOGLE.com. [TTL=300]
10 ASPMX2.GOOGLEMAIL.com. [TTL=300]
10 ASPMX3.GOOGLEMAIL.com. [TTL=300]
|All nameservers have same MX records||Good! All of your nameservers have the same MX records.|
|All MX records contain valid hostnames||Good! All of your MX entries have valid hostnames (e.g. are not IP's or invalid domain names).|
|All MX records use public IP addresses||Good! All of your MX entries have public IP addresses.|
|MX record is not a CNAME/alias||Good! When querying for your MX records we did not receive a CNAME record as a result.|
|MX A records are not CNAME's||Good! No CNAME records are present for your MX A records.|
|Number of MX records||Good! 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!|
|Duplicate MX A records||Good! No two MX records resolve to the same IP address.|
|Differing MX A records||Good! You have no different IP's for your MX A records than the DNS server that is authoritive for that hostname.|
|MX records have reverse DNS entries||Good! All your MX IP addresses have reverse DNS entries. The reverse entries returned were:|
220.127.116.11.in-addr.arpa <--> qa-in-f26.1e100.net.
18.104.22.168.in-addr.arpa <--> wi-in-f27.1e100.net.
22.214.171.124.in-addr.arpa <--> ee-in-f27.1e100.net.
126.96.36.199.in-addr.arpa <--> wi-in-f26.1e100.net.
188.8.131.52.in-addr.arpa <--> ee-in-f26.1e100.net.