GoDaddy -- This makes no sense to me

[godinu]

let me preface this by saying I've bought hundreds of domains, most through Go Daddy, in the past few years, and I usually park them right away unless I have immediate plans for the name. Today I bought 3 domains at the same time, then a few hours later, changed the nameservers on each because so a friend could start adding content. I'd only actually checked one of the urls before that and noticed it had a Go Daddy parking page in its place.

Anyway, after changing the nameservers, i notice 2 of the 3 urls still have "server not found" as if they don't exist. The 3rd had a Go Daddy parking page.

In the past, when i bought domains and immediately switched the nameservers to a parking site, the change happened pretty quickly. The go daddy rep is telling me it will take up to 24 hrs for the dns to resolve. What's up with that? Is that normal now? Out of hundreds of domains I have never had to wait like that. It was always a matter of minutes. Is Go Daddy being ridiculous or is that just how it is with other registrars now too? It would suck to wait 24 hours when you want to do something with a domain.

 

[Swizi]

let me preface this by saying I've bought hundreds of domains, most through Go Daddy, in the past few years, and I usually park them right away unless I have immediate plans for the name. Today I bought 3 domains at the same time, then a few hours later, changed the nameservers on each because so a friend could start adding content. I'd only actually checked one of the urls before that and noticed it had a Go Daddy parking page in its place.

Anyway, after changing the nameservers, i notice 2 of the 3 urls still have "server not found" as if they don't exist. The 3rd had a Go Daddy parking page.

In the past, when i bought domains and immediately switched the nameservers to a parking site, the change happened pretty quickly. The go daddy rep is telling me it will take up to 24 hrs for the dns to resolve. What's up with that? Is that normal now? Out of hundreds of domains I have never had to wait like that. It was always a matter of minutes. Is Go Daddy being ridiculous or is that just how it is with other registrars now too? It would suck to wait 24 hours when you want to do something with a domain.

That's very normal. It can actually take up to 72 hours.
Like it or lump it, you're going to have to wait.

 

[shockie]

you have to wait for them to resolve no matter where your domains are registered, and the length of time taken is quite independent of registrar.

 

[Krossat]

It can take upto 72 hrs as Swizi mentioned.
But do try clearing your Internet Explorer cache, it dosent refresh pages sometime, your domains might already be up.

 

[godinu]

thanks all. Maybe I'm just remembering incorrectly, or was very lucky in the past with previous domain purchases.

 

[antic]

thanks all. Maybe I'm just remembering incorrectly, or was very lucky in the past with previous domain purchases.

Who is your regisatrar?

 

[Dave_Z]

Who is your regisatrar?

The OP already stated who. Read it again if you have to.

As the others stated, godinu, give it time. No one fully controls over how soon
a newly registered domain name will resolve to its intended destination online,
although there are certain things you can do in case the domain name is using
the correct nameservers by then.

 

[Hycari]

Like the others have said, it takes time for the DNS to propagate, and it also depends on how physically close to the servers you are. DNS propagation is really under no ones control, so you have no choice but to wait. It has nothing to do with the Registrar or the host.

 

[iHubNet-Matt]

changing the nameservers is different from adding them for a fresh domain.
In this case, you were having the dodadyy nameservers and later you changed it to your's.
In this case first nameservers will be cached in different caching servers including the one in your ISP. So data has to get expired from all the caching nameservers. may be the domain will be resolving correctly for me, but you will have a cached value as you had visited the domain earlier.
In that case there is nothing other than waiting until the dns get globally propagated.

 

[loran76]

In that case there is nothing other than waiting until the dns get globally propagated.

It's the worst that can be IMHO.