View Single Post
  #5  
Old 14th November 2011, 14:29
psychop psychop is offline
Member
 
Join Date: Apr 2010
Posts: 33
Thanks: 0
Thanked 0 Times in 0 Posts
Default

DNS records for one site looks like this:
Code:
Domain NS records 	Nameserver records returned by the parent servers are:

ns1.server.com.   ['9x.1x.xx.xx'] (NO GLUE)   [TTL=86400]
ns2.server.com.   ['9x.1x.xx.xx'] (NO GLUE)   [TTL=86400]

Pass 	Your nameservers are listed 	Good. The parent server ns8.arnes.si 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 ns8.arnes.si 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 nameservers	NS records got from your nameservers listed at the parent NS are:

ns1.server.com  ['9x.1x.xx.xx']   [TTL=86400]
ns2.server.com  ['9x.1x.xx.xx']   [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:
9x.1x.xx.xx
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.
Pass 	Missing nameservers reported by parent 	OK. All NS records are the same at the parent and at your nameservers.
Pass 	Missing nameservers reported by your nameservers 	OK. All nameservers returned by the parent server ns8.arnes.si are the same as the ones reported by your nameservers.
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.
Warn 	Different subnets 	WARNING: Not all of your nameservers are in 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.
Warn 	Different autonomous systems 	WARNING: Single point of failure
Pass 	Stealth NS records sent 	Ok. No stealth ns records are sent
SOA 	Info 	SOA record	The SOA record is:
Primary nameserver: ns1.server.com
Hostmaster E-mail address: admin@email.com
Serial #: 2011111302
Refresh: 28800
Retry: 7200
Expire: 604800   1 weeks
Default TTL: 86400
Pass 	NSs have same SOA serial 	OK. All your nameservers agree that your SOA serial number is 2011111302.
Pass 	SOA MNAME entry 	OK. ns1.server.com That server is listed at the parent servers.
Pass 	SOA Serial 	Your SOA serial number is: 2011111302. This appears to be in the recommended format of YYYYMMDDnn.
Pass 	SOA REFRESH 	OK. Your SOA REFRESH interval is: 28800. That is OK
Pass 	SOA RETRY 	Your SOA RETRY value is: 7200. Looks ok
Pass 	SOA EXPIRE 	Your SOA EXPIRE number is: 604800.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 Records	Your MX records that were reported by your nameservers are:

20   ns1.server.com   9x.1x.xx.xx
10   aspmx.l.google.com   74.125.39.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. ]
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.
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 	Good. Looks like you have multiple MX records at all your nameservers. This is a good thing and will help in preventing loss of mail.
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:
183.132.103.93.in-addr.arpa ->  9x-1x-xx-xx.static.isp.net
27.39.125.74.in-addr.arpa ->  fx-in-f27.1e100.net
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW 	Info 	WWW A Record 	Your www.mysite.com A record is:
www.mysite.com  [9x.1x.xx.xx] 
Pass 	IPs are public 	OK. All of your WWW IPs appear to be public IPs.
Pass 	WWW CNAME 	OK. No CNAME
Reply With Quote