Hello,

When you get a new domain it normally takes upto 48 hours to be poniting to the server correctly, I just bought the domain histyle.biz and it took 5 Minutes!! I am amazed!

Yay Godaddy.

Or maybe just done at the same time my Godaddy update their files and same time my ISP updates the DNS. ??

.biz, .info (and .name, I guess) are propagated in a matter of minutes, yes It's not just GoDaddy...

coool! that's something new ... tks for sharing

Originally posted by cyansmoker
.biz, .info (and .name, I guess) are propagated in a matter of minutes, yes It's not just GoDaddy...

Are you sure about that? I've registered a .biz at GoDaddy before, and it didn't take a few minutes. Maybe you two just got lucky and registered a few minutes before the .biz servers updated? :)

it doesn't
i have a .biz (gotosite.biz) at godaddy and it usally takes about 24 hours:(

i had a .com propogate in 30 minutes once it all depends on your isp really

Originally posted by 9onlinehost
i had a .com propogate in 30 minutes once it all depends on your isp really
Complete worldwide propagation in 30 minutes ?? :eek:

not complete worldwide but to my isp :D

:D Nice isp you have there :D

Originally posted by 9onlinehost
not complete worldwide but to my isp :D

For me it usually takes around 2 hours for new domain names (including .com and .biz).

at the end of the day, it makes no difference where the domain is registered, as the only reason why you have to wait for a domain to work is for the DNS to propogate and for each ISP to update their DNS databases.

It's pot luck!

Mine works after 11pm each day :)

Well,
it's been observed that .info domains, for instance, are propagated much faster.
Now, if may be that if you live in a particularly remote are your local NS will be updated after a long delay. But still...

.biz info is kept in one location (at NeuLevel) and not distributed like .com. I met withthe NeuLevel people at last year's HostingExpo in DC and they were claiming 15-minute propagation for new registrations and DNS changes. Period. Looks like it is true after all. I imagine any new TLD will have the same functionality, why go back to an old system that can take days?

Course, if NeuLevel's DB servers should ever go down...ouch.

Okay, either I've been severely misinformed, or you guys don't understand propagation at all. What does any of this have to do with your ISP? Do you guys actually think all DNS changes have to propagate to every DNS server in the world? Not only is that impractical, it's also impossible.

ocne i chnaged dns servers of my .biz and it propogated in 30mins:rolleyes:

Originally posted by ToastyX
Okay, either I've been severely misinformed, or you guys don't understand propagation at all. What does any of this have to do with your ISP? Do you guys actually think all DNS changes have to propagate to every DNS server in the world? Not only is that impractical, it's also impossible.

Yes but many ISP's cache commonly-accessed DNS info. For example, when I change nameservers or get new domains, it takes a few hours. I can goto www.anonimizer.com and see that the change has been made. The trouble is, it takes a few days before I can type the domain into IE and get to the new site (btw the site itself isnt cached on my computer either) :)

Originally posted by ToastyX
Okay, either I've been severely misinformed, or you guys don't understand propagation at all. What does any of this have to do with your ISP? Do you guys actually think all DNS changes have to propagate to every DNS server in the world? Not only is that impractical, it's also impossible.

You've been severely misinformed ;)

It's just that's it's not a push propagation but a pull propagation.

There have been numerous occasions when a customer of ours has reported that the DNS change that they made to their domain several days ago, has still not propogated, but when I view the domain it has.

If the customer accesses the net through a different ISP, it works, but with another it doesn't.

It is true that most ISP's cache certain data.

DNS is a marvellous thing and damn annoying!! :mad:

Originally posted by Mester


Yes but many ISP's cache commonly-accessed DNS info. For example, when I change nameservers or get new domains, it takes a few hours. I can goto www.anonimizer.com and see that the change has been made. The trouble is, it takes a few days before I can type the domain into IE and get to the new site (btw the site itself isnt cached on my computer either) :)

Of course most ISPs cache DNS information. That's how DNS is meant to work, but we were talking about new domain name registrations. How can a new domain name be "commonly-accessed" if it's new? ;) That's not how caching works anyway.

Originally posted by cyansmoker


You've been severely misinformed ;)

It's just that's it's not a push propagation but a pull propagation.

I'm not sure if you understand how DNS works. When you register a domain name or change the DNS servers for a domain name, those changes have to propagate to all of the DNS servers that handle the TLD. That's propagation. It has nothing to do with your ISP, nor does it have anything to do with your location. If your ISP's DNS server has the record cached, it returns the cached record, otherwise, it queries the appropriate DNS servers to find the record. The DNS server that has authority over whatever host name that was queried tells other DNS servers how long to cache the record. That doesn't really have anything to do with propagation. That's just caching.

The 13 DNS servers that handle .com, .net, and .org domain names handle thousands of domain names. With that many DNS servers and domain names, it'd be a waste of resources to update every few minutes. That's why propagation for .com, .net, and .org domain names takes so long.

Originally posted by joelmoss
There have been numerous occasions when a customer of ours has reported that the DNS change that they made to their domain several days ago, has still not propogated, but when I view the domain it has.

If the customer accesses the net through a different ISP, it works, but with another it doesn't.

It is true that most ISP's cache certain data.

DNS is a marvellous thing and damn annoying!! :mad:

The DNS servers that handle .com, .net, and .org domain names have the TTL for NS records set to two days. The DNS servers that handle .biz have the TTL for NS records set to 15 minutes. The DNS servers that handle .info have the TTL for NS records set to 22.8 hours. That's how long other DNS servers are supposed to cache those NS records. If those NS records are never checked, they are never cached, which is why when a customer of yours makes a name server change to their domain, it can take up to a couple of days for them to see the change on their main ISP while they can already see the change on another ISP. Their main ISP's DNS servers had the old NS records cached, while the other ISP's DNS servers didn't. That doesn't really have anything to do with propagation. That's just caching. It's also possible to cache negative answers, so someone that's eager to see if their new domain name is working can actually cache a "host not found" kind of message on their ISP's DNS servers, making it take even longer until they can see their domain working.

DNS isn't annoying. I think DNS is one of the few things in this world that was designed pretty well. :)

Sorry about so many posts. I just like DNS so much. :) If I messed up anywhere, correct me.

Originally posted by ToastyX


I'm not sure if you understand how DNS works.
And yet it seems to me we're all basically saying the same things ;)

Originally posted by ToastyX


The 13 DNS servers that handle .com, .net, and .org domain names handle thousands of domain names.
:D :D :D

The only confusion that still lingers in this thread is talking about caching in the context of new domains being added to the Zone files.

There is no time required to clear the caches at anyone's ISP when a new domain is added.

This is how new domains can show up clean in 24 hours, and how changes can sometimes take weeks if the cache at your (or some elses) ISP is incorrectly managed.

-t