domain name

has anybody ever used http://www.godaddy.com domain names. I just purchased one, but im having trouble getting it to work. it wont send it to my site. i have the name servers and everything. if anybody could help it would be great.

thx
poly

I have used GoDaddy. It's a great service in my opinion.

Anyways, you need to wait around 72 hours for your domain name to point to your nameservers. Check it in about 3 days and it should work.

arite, its been about 48 hours, the site says 24. How long did yours take?

thx
poly

The average time is between 24-72 hours. What's the domain name? I'll check it from where I am

//I used godaddy before. I usually can access within 24 hours, but a friend of mine usually takes 2 or 3 days. Pretty much normal.

Mine took about 72 hours. It really depends on where you are in the world. Be patient and if nothing happen in 72 hours, post again.

Just a note of possible interest.

The old 48-72 hour rule no longer applies to .com/net domains thanks to the verisign rapid update.

http://www.verisign.com/products-servic ... 05514.html

I've noticed newley registered domains and changes to registered domains resolving within less than 5 minutes for these TLD's

the domain is http://www.thesoccermall.net and its been over 72 hours now and it still dosent work.

poly

Whois shows the following name servers.

Domain servers in listed order:
NS1.SHYPER.COM
NS2.SHYPER.COM

Are these correct.

dnsreport dot com show serious problems with that sites dns set-up.

http://dnsreport.com/tools/dnsreport.ch ... ermall.net

I do not think the problem lies with Godaddy at all but the dns zone where your domain is supposed to be hosted.

The nameservers registered to your domain are not answering requests for that domain. I would contact your web host and see what is happening there.

At Poly's request I corrected a small problem with the domain forwarding on that this morning at godaddy. It should redirect to thesoccermall.shyper.com within the normal propogation time, probably within the next day or so.

Hi,
Are you sure that your site is hosted on the servers that it is pointing at? Here is what I found out about it.
DNS server ns1.shyper.com[67.15.53.105] is alive, but not authoritative for domain 'thesoccermall.net' and didn't return SOA
DNS server ns2.shyper.com[67.15.53.106] is alive, but not authoritative for domain 'thesoccermall.net' and didn't return SOA
0 server(s) are alive
No DNS servers alive, tests stopped.
The servers are OK but they don't seem to know your site. This has nothing to do with the registrer of your site. Please get in touch with your host.

ok i sent my host an email and ill see what is going on. i looked at that report and sent a copy to my host. if they dont get if fixed, ill just move my stuff to a new host.

poly

Alright, good to know. Good luck with your host!

thx man

poly

I think the problem is a little more serious than that. It's their domain and/or nameservers that are screwed up:


ERROR: ns1.shyper.com. has a CNAME entry (shyper.com.); it is not valid to have a CNAME entry and NS entries for ns1.shyper.com.. See RFC1912 2.4 and RFC2181 10.3 for more information.
ERROR: ns2.shyper.com. has a CNAME entry (shyper.com.); it is not valid to have a CNAME entry and NS entries for ns2.shyper.com.. See RFC1912 2.4 and RFC2181 10.3 for more information.

If you ping ns1.shyper.com and ns2.shyper.com the response comes from shyper.com and what's worse the same IP 67.15.53.107.

I don't think they know what they're doing sweetie ...

OK -- I think I figured this out. I was a little swamped this morning and when I tried to help Poly out wasn't thinking through things, but after reading the additional information I think I know what happened. What poly asked me to do was check the name servers at godaddy and make sure the forwarding was set correctly. The name servers Poly gave my were the ns.shyper one's and the forwarding should have been set up to forward thesoccermall.net to thesoccermall.shyper.com (that was slightly incorrect so I fixed that). However after reading the most recent posts I realized what's happening. In order for godaddy to forward, the name server records need to be their DNS servers so that http://www.thesoccermall.net resolves to godaddy's name servers in which case they would then be able to forward appropriately. As it stands right now, the name servers at godaddy are set to resolve to shyper, in which case that explains why there is no resolution since, as noted, there are no cname records at shyper to resolve it.

I guess we need to decide if we want godaddy to forward it or to set up a cname for it and use shyper's name servers. You following me on that Poly?