co.cc domain

[laozing]

So... Is this issue gonna be fixed anytime soon? I still can't see it and apparently neither some friends of mine too.. For some reason though, google was able to pick it up and I guess the googlebot was able to view it. WHY not me? Dns issues?

 

(update) I just did a check on it and got wierd results:

 

Parent Parent Zone The calculated parent zone for your domain is co.cc.

Parent NS records The parent zone DNS server a5.nstld.com. says that your DNS are:

 

NS2.co.cc. [Glue: 222.122.6.21] [TTL: 172800]

NS1.co.cc. [Glue: 222.122.6.20] [TTL: 172800]

 

TLD Parent Check WARNING: Looks like the parent servers do not have information for your TLD when asked. This is ok but can be confusing.

Your nameservers are listed Good. The parent server a5.nstld.com. 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.

Parent sent glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of all 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).

DNS servers have A records All your DNS servers have A records at the zone parent servers. A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers.

NS Your NS records Your DNS servers return the following NS records:

NS2.co.cc.:

 

NP

 

NS1.co.cc.:

 

NP

 

Open DNS servers All of your nameservers don't accept recursive queries. This is very good, since can cause problems (anyone could use them) and can cause Denial of Service attacks.

Mismatched glue All the glues sent by parent zone name servers are identical to the A records present in your DNS servers.

NS A records at nameservers Your nameservers do include A records when they are asked for your NS records. This ensures that your DNS servers know the A records of all your NS records.

All nameservers report identical NS records The NS records at all your nameservers are identical.

All nameservers respond The following nameservers did not respond to my query:

NS2.co.cc.

NS1.co.cc.

 

.

Nameserver name validity All of the NS records that your nameservers report seem valid hostnames.

Number of nameservers You have 2 nameservers. You must have at least 2 nameservers and no more than 7.

Lame nameservers All the nameservers listed at the parent servers answer authoritatively for your domain.

Missing (stealth) nameservers All of your nameservers are listed at the parent zone servers.

Missing (stealth) nameservers 2 I have detected 2 stealth nameservers:

NS2.co.cc.

NS1.co.cc.

 

. These are listed in the parent zone nameservers but are missing in your nameservers

No CNAMEs for domain There are no CNAMEs for turoksite.co.cc.. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.

Nameservers on separate class C's You have nameservers on different Class C IP ranges. This is a must if you want to be found in the case of outage, or even worst, problems!

All NS IPs public All of your NS records appear to use public IPs.

TCP Allowed I cannot test to see if your nameservers accept all TCP connections, because I am not able to get the Ip addresses of your nameservers

SOA Your SOA records Your DNS servers return the following SOA records:

NS2.co.cc.:

 

NP

 

NS1.co.cc.:

 

NP

 

All same SOA I can't test your SOA records as I don't have it!

Same Serial Number I can't test your SOA serials as I don't have them!

SOA Primary NS I can't test your SOA primary NS as I don't have them!

Hostmaster Email I can't test the hostmaster email address as I don't have them!

Serial Format Since I haven't found your SOA records or your SOA serial number, I can't perform this check!

REFRESH Since I haven't found your SOA records or your SOA refresh value, I can't perform this check!

RETRY Since I haven't found your SOA records or your SOA retry value, I can't perform this check!

EXPIRE Since I haven't found your SOA records or your SOA expire value, I can't perform this check!

Default TTL Since I haven't found your SOA records or your SOA Default TTL value, I can't perform this check!

MX Your MX records Your DNS servers return the following MX records:

NS2.co.cc.:

 

NP

 

NS1.co.cc.:

 

NP

 

Multiple MX records It seems you don't have MX records. This means that all the emails sent to your domain will be sent to the A record of your domain (if present), accordingly to RFC 2821 section "5. Address Resolution and Mail Handling".

Invalid characters I don't have MX records to check

All MX IPs public Your NS don't return their IPs when looking explicitly for MX records.

MX records are not CNAMEs I don't have MX records to check

MX A lookups have no CNAMEs I don't have MX records to check

MX is host name, not IP I don't have MX records to check

Differing MX-A records I don't have MX records to check

Duplicate MX records I don't have MX records to check

Reverse DNS entries for MX records I don't have MX records to check

MAIL Connect to mail servers I don't have mailservers to check.

Mail server host name in greeting I have no mail servers to check

Acceptance of NULL <> sender I have no mail servers to check

Acceptance of postmaster address I have no mail servers to check

Acceptance of abuse address I have no mail servers to check

Acceptance of domain literals I have no mail servers to check

Open relay test I have no mail servers to check

SPF record You don't have a SPF record for the domain turoksite.co.cc., meaning that you are not using the protection given from this kind of technology. This is only a warning, but please consider in implementing it!

 

I dont know it says ns1.co.cc but I checked back and it says I have my ns at heliohost so whats going on??? does this site have cname? rather do the domain thing that way as dns is infuriating me.

[Ashoat]

This issue should be fixed now.