I have registered a domain called ferdionwebdesign.com (through godaddy) and I am trying to set up my name servers for it. Right now, I have set up my 2 name servers as ns1.ferdionwebdesign.com (my computer) and I am using xname.org as my second server (ns0.xname.org).
Here is the problem: I cannot connect to my site using my domain name (ferdionwebdesign.com) yet I can connect to it using my external IP address from my internal network behind a router. I used DNSstuff to check if my name servers are working and this is what I am getting the following fails/warns using the dns tool:
INFO NS records at parent servers Your NS records at the parent servers are:
ns1.ferdionwebdesign.com. [188.8.131.52] [TTL=172800] [CA]
ns1.xname.org. [184.108.40.206 (NO GLUE)] [FR]
[These were obtained from i.gtld-servers.net]
WARN Glue at parent nameservers WARNING. The parent servers (I checked with i.gtld-servers.net.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
NS INFO NS records at your nameservers Your 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]
WARN All nameservers report identical NS records WARNING: 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).
220.127.116.11 returns 0 answers (may be a referral)
18.104.22.168 returns 0 answers (may be a referral)
FAIL Lame nameservers ERROR: 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:
FAIL Missing nameservers 2 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:
WARN Nameservers on separate class C's WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Class C ranges. 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.
WARN Single Point of Failure WARNING: Although you have at least 2 NS records, they may both point to the same server (one of our two tests shows them being the same, the other could not complete the test), which would result in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.
SOA FAIL SOA Record No valid SOA record came back:
is not ferdionwebdesign.com.
I also did a trace route on both my nameserver and external IP and each time it seems to abort after reaching a certain host (dx1bb-g15.no.shawcable.net). This seems strange because this seems to be a hostname from my internet provider (Shaw Cable). Each tool I have used either times out or abort after this computer is reached.
When I use a ping tool from the Internet, it times out for each packet (http://webtools.live...com/nt_ping.php); it doesn't matter if I try to ping my IP address or nameserver.
I have been trying and am hoping that someone can help me. Please let me know if you need more info and I will give it to you.