Quote:
Originally Posted by chandrika
Yes I hadnt thought of how it would affect my adsense status.
In fact since this happened, I have found two more strange domains displaying my site.
durmakyokyoladevam dot com
ipinikoparan dot com
.
|
Well your domain seems to have a few oddities with it's DNS servers!
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.
Your NS records at the parent servers are:
ns1.clareross.com. [75.127.68.74] [TTL=172800] [US]
ns2.clareross.com. [75.127.68.75] [TTL=172800] [US]
[These were obtained from h.gtld-servers.net]
And most importantly..
ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are:
Server 75.127.68.74 reports that it will do recursive lookups. [test] Server 75.127.68.75 reports that it will do recursive lookups.
ERROR: Although you have at least 2 NS records, they both point to the same server, resulting in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.
So it looks like you have an error within the DNS servers that are pointing to your domain..
ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries/* (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough)*/. 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. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if you recently changed your reverse DNS entry (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:
78.68.127.75.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]
So I hope this can help you out by solving the problem for you, those of us that own and run search engines are usually quite clued up..
All the best
Dave Andrews from down in New Zealand..