مشکل جدی با dns سرور و سایت ها (فوری)

باسلام دوستان عزیز
من یک سایت توی سرورم اوکی کردم و توی وبمستر که حالا ست کردم سایت رو یک اروری داده:
توی قسمت DNS
ارور googlebot cant access your site
من آدر سایتم رو هم زدم توی سایت
intoDNS: checks DNS and mail servers health
بعد مواردی که اومد به این شکل بود

Parent http://www.intodns.com/static/images/info.gif Domain NS records Nameserver records returned by the parent servers are:

ns1.xx.com. ['My Ip'] [TTL=172800]
ns2.x.com. ['My Ip] [TTL=172800]

c.gtld-servers.net was kind enough to give us that information.

http://www.intodns.com/static/images/pass.gif TLD Parent Check Good. c.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.

http://www.intodns.com/static/images/pass.gif Your nameservers are listed Good. The parent server c.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.

http://www.intodns.com/static/images/pass.gif 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)

http://www.intodns.com/static/images/pass.gif Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.

NS http://www.intodns.com/static/images/info.gif NS records from your nameservers NS records got from your nameservers listed at the parent NS are:

ns2.xx.com ['My Ip'] [TTL=86400]
ns1.xx.com ['My Ip'] [TTL=86400]

http://www.intodns.com/static/images/pass.gif Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.

http://www.intodns.com/static/images/pass.gif 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!

http://www.intodns.com/static/images/pass.gif 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.

http://www.intodns.com/static/images/pass.gif Mismatched NS records OK. The NS records at all your nameservers are identical.

http://www.intodns.com/static/images/error.gif DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
My Ip

http://www.intodns.com/static/images/pass.gif Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.

http://www.intodns.com/static/images/pass.gif 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.

http://www.intodns.com/static/images/pass.gif Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.

http://www.intodns.com/static/images/pass.gif Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.

http://www.intodns.com/static/images/pass.gif Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server c.gtld-servers.net are the same as the ones reported by your nameservers.

http://www.intodns.com/static/images/pass.gif 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.

http://www.intodns.com/static/images/pass.gif 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.

http://www.intodns.com/static/images/warn.gif Different subnets WARNING: Not all of your nameservers are in different subnets

http://www.intodns.com/static/images/pass.gif 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

http://www.intodns.com/static/images/pass.gif 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.

http://www.intodns.com/static/images/warn.gif Different autonomous systems WARNING: Single point of failure

http://www.intodns.com/static/images/pass.gif Stealth NS records sent Ok. No stealth ns records are sent

SOA http://www.intodns.com/static/images/info.gif SOA record The SOA record is:
Primary nameserver: ns1.xxx.com
Hostmaster E-mail address: xxx.gmail.com
Serial #: 2012092601
Refresh: 86400
Retry: 7200
Expire: 3600000 5 weeks
Default TTL: 86400

http://www.intodns.com/static/images/pass.gif NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2012092601.

http://www.intodns.com/static/images/pass.gif SOA MNAME entry OK. ns1.xxx.com That server is listed at the parent servers.

http://www.intodns.com/static/images/pass.gif SOA Serial Your SOA serial number is: 2012092601. This appears to be in the recommended format of YYYYMMDDnn.

http://www.intodns.com/static/images/pass.gif SOA REFRESH OK. Your SOA REFRESH interval is: 86400. That is OK

http://www.intodns.com/static/images/pass.gif SOA RETRY Your SOA RETRY value is: 7200. Looks ok

http://www.intodns.com/static/images/warn.gif SOA EXPIRE Your SOA EXPIRE number is: 3600000. That is NOT OK

http://www.intodns.com/static/images/pass.gif 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 http://www.intodns.com/static/images/info.gif MX Records Your MX records that were reported by your nameservers are:

0 downp30.com 5.135.60.166

[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. ]

http://www.intodns.com/static/images/pass.gif 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

http://www.intodns.com/static/images/pass.gif MX name validity Good. I did not detect any invalid hostnames for your MX records.

http://www.intodns.com/static/images/pass.gif MX IPs are public OK. All of your MX records appear to use public IPs.

http://www.intodns.com/static/images/pass.gif MX CNAME Check OK. No problems here.

http://www.intodns.com/static/images/pass.gif MX A request returns CNAME OK. No CNAMEs returned for A records lookups.

http://www.intodns.com/static/images/pass.gif MX is not IP OK. All of your MX records are host names.

http://www.intodns.com/static/images/info.gif Number of MX records OK. Looks like you only have one MX record at your nameservers. You should be careful 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.

http://www.intodns.com/static/images/pass.gif Mismatched MX A OK. I did not detect differing IPs for your MX records.

http://www.intodns.com/static/images/pass.gif Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.

http://www.intodns.com/static/images/error.gif Reverse MX A records (PTR) ERROR: No reverse DNS (PTR) entries. The problem MX records are:
xxx.in-addr.arpa -> no reverse (PTR) detected
You should contact your ISP and ask him to add a PTR record for your ips

WWW http://www.intodns.com/static/images/info.gif WWW A Record ]

[Looks like you have CNAME's]

http://www.intodns.com/static/images/pass.gif IPs are public OK. All of your WWW IPs appear to be public IPs.

http://www.intodns.com/static/images/pass.gif WWW CNAME OK. You do have a CNAME record for www.downp30.com.Your CNAME entry also returns the A record for the CNAME entry, which is good.

دوستان دامین ان اس ریکوردم مشکل داره که آی پی هارو روش ست کردم میشه یک راهنمایی بفرمایید دوستان؟

Parent	http://www.intodns.com/static/images/info.gif	Domain NS records	Nameserver records returned by the parent servers are: ns1.xx.com. ['My Ip'] [TTL=172800] ns2.x.com. ['My Ip] [TTL=172800] c.gtld-servers.net was kind enough to give us that information.
http://www.intodns.com/static/images/pass.gif	TLD Parent Check	Good. c.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.
http://www.intodns.com/static/images/pass.gif	Your nameservers are listed	Good. The parent server c.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.
http://www.intodns.com/static/images/pass.gif	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)
http://www.intodns.com/static/images/pass.gif	Nameservers A records	Good. Every nameserver listed has A records. This is a must if you want to be found.
NS	http://www.intodns.com/static/images/info.gif	NS records from your nameservers	NS records got from your nameservers listed at the parent NS are: ns2.xx.com ['My Ip'] [TTL=86400] ns1.xx.com ['My Ip'] [TTL=86400]
http://www.intodns.com/static/images/pass.gif	Recursive Queries	Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
http://www.intodns.com/static/images/pass.gif	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!
http://www.intodns.com/static/images/pass.gif	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.
http://www.intodns.com/static/images/pass.gif	Mismatched NS records	OK. The NS records at all your nameservers are identical.
http://www.intodns.com/static/images/error.gif	DNS servers responded	ERROR: One or more of your nameservers did not respond: The ones that did not respond are: My Ip
http://www.intodns.com/static/images/pass.gif	Name of nameservers are valid	OK. All of the NS records that your nameservers report seem valid.
http://www.intodns.com/static/images/pass.gif	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.
http://www.intodns.com/static/images/pass.gif	Nameservers are lame	OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
http://www.intodns.com/static/images/pass.gif	Missing nameservers reported by parent	OK. All NS records are the same at the parent and at your nameservers.
http://www.intodns.com/static/images/pass.gif	Missing nameservers reported by your nameservers	OK. All nameservers returned by the parent server c.gtld-servers.net are the same as the ones reported by your nameservers.
http://www.intodns.com/static/images/pass.gif	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.
http://www.intodns.com/static/images/pass.gif	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.
http://www.intodns.com/static/images/warn.gif	Different subnets	WARNING: Not all of your nameservers are in different subnets
http://www.intodns.com/static/images/pass.gif	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
http://www.intodns.com/static/images/pass.gif	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.
http://www.intodns.com/static/images/warn.gif	Different autonomous systems	WARNING: Single point of failure
http://www.intodns.com/static/images/pass.gif	Stealth NS records sent	Ok. No stealth ns records are sent
SOA	http://www.intodns.com/static/images/info.gif	SOA record	The SOA record is: Primary nameserver: ns1.xxx.com Hostmaster E-mail address: xxx.gmail.com Serial #: 2012092601 Refresh: 86400 Retry: 7200 Expire: 3600000 5 weeks Default TTL: 86400
http://www.intodns.com/static/images/pass.gif	NSs have same SOA serial	OK. All your nameservers agree that your SOA serial number is 2012092601.
http://www.intodns.com/static/images/pass.gif	SOA MNAME entry	OK. ns1.xxx.com That server is listed at the parent servers.
http://www.intodns.com/static/images/pass.gif	SOA Serial	Your SOA serial number is: 2012092601. This appears to be in the recommended format of YYYYMMDDnn.
http://www.intodns.com/static/images/pass.gif	SOA REFRESH	OK. Your SOA REFRESH interval is: 86400. That is OK
http://www.intodns.com/static/images/pass.gif	SOA RETRY	Your SOA RETRY value is: 7200. Looks ok
http://www.intodns.com/static/images/warn.gif	SOA EXPIRE	Your SOA EXPIRE number is: 3600000. That is NOT OK
http://www.intodns.com/static/images/pass.gif	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	http://www.intodns.com/static/images/info.gif	MX Records	Your MX records that were reported by your nameservers are: 0 downp30.com 5.135.60.166 [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. ]
http://www.intodns.com/static/images/pass.gif	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
http://www.intodns.com/static/images/pass.gif	MX name validity	Good. I did not detect any invalid hostnames for your MX records.
http://www.intodns.com/static/images/pass.gif	MX IPs are public	OK. All of your MX records appear to use public IPs.
http://www.intodns.com/static/images/pass.gif	MX CNAME Check	OK. No problems here.
http://www.intodns.com/static/images/pass.gif	MX A request returns CNAME	OK. No CNAMEs returned for A records lookups.
http://www.intodns.com/static/images/pass.gif	MX is not IP	OK. All of your MX records are host names.
http://www.intodns.com/static/images/info.gif	Number of MX records	OK. Looks like you only have one MX record at your nameservers. You should be careful 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.
http://www.intodns.com/static/images/pass.gif	Mismatched MX A	OK. I did not detect differing IPs for your MX records.
http://www.intodns.com/static/images/pass.gif	Duplicate MX A records	OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
http://www.intodns.com/static/images/error.gif	Reverse MX A records (PTR)	ERROR: No reverse DNS (PTR) entries. The problem MX records are: xxx.in-addr.arpa -> no reverse (PTR) detected You should contact your ISP and ask him to add a PTR record for your ips
WWW	http://www.intodns.com/static/images/info.gif	WWW A Record	] [Looks like you have CNAME's]
http://www.intodns.com/static/images/pass.gif	IPs are public	OK. All of your WWW IPs appear to be public IPs.
http://www.intodns.com/static/images/pass.gif	WWW CNAME	OK. You do have a CNAME record for www.downp30.com.Your CNAME entry also returns the A record for the CNAME entry, which is good.