Dns Report - yahova.net

New Search

Category	Test name	Information
Parent	Domain NS records	Nameserver records returned by the parent servers are: ns1.shahidhemmat.com. ['173.45.83.234'] [TTL=172800] ns2.shahidhemmat.com. ['173.45.83.235'] [TTL=172800] d.gtld-servers.net was kind enough to give me that information.
	TLD Parent Check	Good. d.gtld-servers.net, the parent server I interogated, 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.
	Your nameservers are listed	Good. The parent server d.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.
	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)
	Nameservers A records	Good. Every nameserver listed has A records. This is a must if you want to be found.
NS	NS records from your nameservers	NS records got from your nameservers listed at the parent NS are: ns2.mibonet.com. ['ns2.mibonet.com'] [TTL=14400] ns1.mibonet.com. ['ns1.mibonet.com'] [TTL=14400]
	Recursive Queries	Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
	Same Glue	Sorry , but the A records (the GLUE) got from the parent zone check are not the same as the ones got from your nameservers.
	Glue for NS records	OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
	Mismatched NS records	Sorry. The NS records at one or more your nameservers are not identical.
	DNS servers responded	Good. All nameservers listed at the parent server responded.

	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.
	Nameservers are lame	OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
	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.mibonet.com ns1.mibonet.com
	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.shahidhemmat.com ns2.shahidhemmat.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).
	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.
	Different subnets	OK. Looks like you have nameservers on different subnets!
	IPs of nameservers are public	Sorry. Looks like one or more IP addresses of your nameservers are private. This is not a good thing because it will cause DNS delays and other problems like
	DNS servers allow TCP connection	OK. Seems all your DNS servers allow TCP connections. This is a good thing and usefull even if UDP connections are used by default.
	Different autonomous systems	OK. It seems you are safe from a single point of failure. You must be carefull about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
	Stealth NS records sent	Stealth NS records were sent: ns1.shahidhemmat.com ns2.shahidhemmat.com
SOA	SOA record	The SOA record is: Primary nameserver: ns1.mibonet.com Hostmaster E-mail address: hostmaster.yahova.net Serial #: 2009060200 Refresh: 14400 Retry: 3600 Expire: 1209600 Default TTL: 86400
	NSs have same SOA serial	OK. All your nameservers agree that your SOA serial number is 2009060200.
	SOA MNAME entry	Sorry, But ns1.mibonet.com is not listed at the parent servers.
	SOA Serial	Your SOA serial number is: 2009060200. This appears to be in the recommended format of YYYYMMDDnn.
	SOA REFRESH	OK. Your SOA REFRESH interval is: 14400. That is OK
	SOA RETRY	Your SOA RETRY value is: 3600. Looks ok
	SOA EXPIRE	Your SOA EXPIRE number is: 1209600.Looks ok
	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). Your value of 86400 is OK.
MX	MX Records	Your MX records that were reported by your nameservers are: 10 mail.yahova.net 173.45.83.234 [These are all the MX records that I found.]
	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
	MX name validity	Good. I did not detect any invalid hostnames for your MX records.>
	MX IPs are public	OK. All of your MX records appear to use public IPs.
	MX is not IP	OK. All of your MX records are host names.
	Number of MX records	OK. Looks like you only have one MX record at your nameservers. You should be carefull 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.
	Reverse MX A records (PTR)	Your reverse (PTR) record: 234.83.45.173.in-addr.arpa -> server.mibonet.com You have reverse (PTR) records for all your IPs, that is a good thing.
WWW	WWW A Record	Your www.yahova.net A record is: www.yahova.net -> [173.45.83.234]

Static Link to the Status and Trends of http://www.yahova.net