my new domin from godaddy is set to use ns1.x10hosting.com & ns2.x10hosting.com i changed my domain in my account here on the forum(not in cpanel) to my new domain "ScuderiaFerrariF1.Net" but for some reason my old x10 domain is still working and my new one isn't.
I done this dns check and it said this
NS
INFONS records at your nameserversYour NS records at your nameservers are:
[None of your nameservers returned your NS records; they could be down or unreachable, or could all be lame nameservers]
PASSOpen DNS serversOK. Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be open DNS servers).
PASSMismatched glueOK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
PASSNo NS A records at nameserversOK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
WARNAll nameservers report identical NS recordsWARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).
72.232.216.108 returns 0 answers (may be a referral)72.232.216.109 returns 0 answers (may be a referral)
PASSAll nameservers respondOK. All of your nameservers listed at the parent nameservers responded.
PASSNameserver name validityOK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASSNumber of nameserversOK. You have 2 nameservers. You must have at least 2 nameservers (
RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
FAILLame nameserversERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
72.232.216.108
72.232.216.109
PASSMissing (stealth) nameserversOK. All 0 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
FAILMissing nameservers 2ERROR: 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.x10hosting.com.
ns2.x10hosting.com.
PASSNo CNAMEs for domainOK. There are no CNAMEs for scuderiaferrarif1.net.
RFC1912 2.4 and
RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASSNo NSs with CNAMEsOK. There are no CNAMEs for your NS records.
RFC1912 2.4 and
RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
WARNNameservers on separate class C'sWARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C (technically, /24) address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location.
RFC2182 3.1 goes into more detail about secondary nameserver location.
PASSAll NS IPs publicOK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
PASSTCP AllowedOK. All your DNS servers allow TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems.
FAILSingle Point of FailureERROR: Although you have 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.
INFONameservers versionsYour nameservers have the following versions:
72.232.216.108: No version info available (does not exist).
72.232.216.109: No version info available (does not exist).
status = "Waiting for SOA responses from your nameservers...";
PASSStealth NS record leakageYour DNS servers do not leak any stealth NS records (if any) in non-NS requests.SOA
FAILSOA RecordNo valid SOA record came back:
is not scuderiaferrarif1.net.
anyone got any idea whats wrong i thought it was cos the dns was down but its now online and my domain still wont work. :dunno:
Also how do point my new domain at the name severs? the only option it gives me on the site where i got it from is which site to forward the domain too?