What's the quickest a domain name has propagated for you?

[N9ne]

I've been setting personal records with ol' Namecheap lately. The last 8 domains I've bought from NameCheap have all propagated within 24 hours, but recently they've been propagating in less than 10. The latest domain I got was propagated in 6 hours or so.

Is this normal nowadays? Are domains propagating super fast?

It's weird, when I was with DirectNIC domains took around 30 hours but with namecheap they're taking a lot less...

Waht's the fastest propagation you've had?

 

[darksk8er]

GamerDesign took 45 Hours before people stop seeing SY4.net

 

[Matt]

lol

 

[ToastyX]

Let's say you're trying to resolve www.example.com.

If the name server(s) (or DNS server(s), same thing) you're using (which is generally your ISP's, but it doesn't have to be; you could run your own or use someone else's) doesn't have the address (A) record for www.example.com cached, it will have to search for the answer. How does it search for the answer? Let's start from scratch.

There are 13 root servers:

A.ROOT-SERVERS.NET. has address 198.41.0.4
B.ROOT-SERVERS.NET. has address 128.9.0.107
C.ROOT-SERVERS.NET. has address 192.33.4.12
D.ROOT-SERVERS.NET. has address 128.8.10.90
E.ROOT-SERVERS.NET. has address 192.203.230.10
F.ROOT-SERVERS.NET. has address 192.5.5.241
G.ROOT-SERVERS.NET. has address 192.112.36.4
H.ROOT-SERVERS.NET. has address 128.63.2.53
I.ROOT-SERVERS.NET. has address 192.36.148.17
J.ROOT-SERVERS.NET. has address 192.58.128.30
K.ROOT-SERVERS.NET. has address 193.0.14.129
L.ROOT-SERVERS.NET. has address 198.32.64.12
M.ROOT-SERVERS.NET. has address 202.12.27.33

The name server you're using asks the root servers for the address (A) record(s) for www.example.com.

The root servers will answer:

com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
com.                    172800  IN      NS      M.GTLD-SERVERS.NET.

A.GTLD-SERVERS.NET.     172800  IN      A       192.5.6.30
B.GTLD-SERVERS.NET.     172800  IN      A       192.33.14.30
C.GTLD-SERVERS.NET.     172800  IN      A       192.26.92.30
D.GTLD-SERVERS.NET.     172800  IN      A       192.31.80.30
E.GTLD-SERVERS.NET.     172800  IN      A       192.12.94.30
F.GTLD-SERVERS.NET.     172800  IN      A       192.35.51.30
G.GTLD-SERVERS.NET.     172800  IN      A       192.42.93.30
H.GTLD-SERVERS.NET.     172800  IN      A       192.54.112.30
I.GTLD-SERVERS.NET.     172800  IN      A       192.43.172.30
J.GTLD-SERVERS.NET.     172800  IN      A       192.48.79.30
K.GTLD-SERVERS.NET.     172800  IN      A       192.52.178.30
L.GTLD-SERVERS.NET.     172800  IN      A       192.41.162.30
M.GTLD-SERVERS.NET.     172800  IN      A       192.55.83.30

Explanation: Those are the name server (NS) records for com and the associated address (A) records. The 172800 tells the name server you're using to cache the record for 172,800 seconds (two days). That is called the TTL (time to live).

Simple explanation: The root servers basically said, "I don't know. Here are the name servers of com and their IP addresses. Ask them. You don't have to ask me for the name servers of com for another two days."

The name server you're using now asks the name servers of com for the address (A) record(s) for www.example.com.

The name servers of com will answer:

EXAMPLE.COM.            172800  IN      NS      a.iana-servers.net.
EXAMPLE.COM.            172800  IN      NS      b.iana-servers.net.

a.iana-servers.net.     172800  IN      A       192.0.34.43
b.iana-servers.net.     172800  IN      A       193.0.0.236

Explanation: Those are the name server (NS) records for example.com and the associated address (A) records (which are called glue records). If the name servers of com did not return glue records, the name server you're using would then have to search for the associated address (A) records.

Simple explanation: The name servers of com basically said, "I don't know. Here are the name servers of example.com and their IP addresses. Ask them. You don't have to ask me for the name servers of example.com for another two days."

The name server you're using now asks the name servers of example.com for the address (A) record(s) for www.example.com.

The name servers of example.com will answer:

WWW.EXAMPLE.COM.        172800  IN      A       192.0.34.166

Explanation: That is the address (A) record of www.example.com. The name server you're using now has the address (A) record of www.example.com cached for two days, unless the cache is flushed or the server is restarted and the cache is not saved.

Simple explanation: The name servers of example.com basically said, "I know! It's 192.0.34.166! You don't have to ask me for the address of www.example.com for another two days." The name server you're using now "remembers" the address of www.example.com for two days. If it "forgets," it can just go through the same process again.

If you register a com domain, the name servers of com are the ones that have to update. Since the name servers of com only update twice a day, you will have to wait until your domain is included before it starts working. Your ISP does not update anything. Nothing "spreads throughout the Internet." Information is gathered as needed.

 

[DaDude]

I have had one propagate in about 2 hours. I was quite amazed by that. I thought it would take at least 10-12 hours.

 

[namemarket]

I have had many websites propogate in SECONDS. That's not a misprint. After changing my nameservers and submittting to Wild West (GoDaddy) the site resolved in seconds, not all the time but sometimes. After the anmeservers are changed I type-in the url and the site pops-up instantly.

Perhaps the fact GoDaddy and myself are both in the same city in Arizona is the reason for it. Can't think of another explanation.

However, I have also had names reg'd at Tucows resolve in minutes at times, and they are in Toronto Canada, a long way from Arizona!

 

[seiya]

Originally posted by NameCaster
I've had them propagate within 2 hours using godaddy or enom.

OMG thats fast, i havent registered a lot lately but 12 hours is the fastest for me

 

[NameCaster]

Originally posted by ToastyX
Let's say you're trying to resolve www.example.com.

If the name server(s) (or DNS server(s), same thing) you're using (which is generally your ISP's, but it doesn't have to be; you could run your own or use someone else's) doesn't have the address (A) record for www.example.com cached, it will have to search for the answer. How does it search for the answer? Let's start from scratch.

There are 13 root servers:

A.ROOT-SERVERS.NET. has address 198.41.0.4
B.ROOT-SERVERS.NET. has address 128.9.0.107
C.ROOT-SERVERS.NET. has address 192.33.4.12
D.ROOT-SERVERS.NET. has address 128.8.10.90
E.ROOT-SERVERS.NET. has address 192.203.230.10
F.ROOT-SERVERS.NET. has address 192.5.5.241
G.ROOT-SERVERS.NET. has address 192.112.36.4
H.ROOT-SERVERS.NET. has address 128.63.2.53
I.ROOT-SERVERS.NET. has address 192.36.148.17
J.ROOT-SERVERS.NET. has address 192.58.128.30
K.ROOT-SERVERS.NET. has address 193.0.14.129
L.ROOT-SERVERS.NET. has address 198.32.64.12
M.ROOT-SERVERS.NET. has address 202.12.27.33

The name server you're using asks the root servers for the address (A) record(s) for www.example.com.

The root servers will answer:

com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
com.                    172800  IN      NS      M.GTLD-SERVERS.NET.

A.GTLD-SERVERS.NET.     172800  IN      A       192.5.6.30
B.GTLD-SERVERS.NET.     172800  IN      A       192.33.14.30
C.GTLD-SERVERS.NET.     172800  IN      A       192.26.92.30
D.GTLD-SERVERS.NET.     172800  IN      A       192.31.80.30
E.GTLD-SERVERS.NET.     172800  IN      A       192.12.94.30
F.GTLD-SERVERS.NET.     172800  IN      A       192.35.51.30
G.GTLD-SERVERS.NET.     172800  IN      A       192.42.93.30
H.GTLD-SERVERS.NET.     172800  IN      A       192.54.112.30
I.GTLD-SERVERS.NET.     172800  IN      A       192.43.172.30
J.GTLD-SERVERS.NET.     172800  IN      A       192.48.79.30
K.GTLD-SERVERS.NET.     172800  IN      A       192.52.178.30
L.GTLD-SERVERS.NET.     172800  IN      A       192.41.162.30
M.GTLD-SERVERS.NET.     172800  IN      A       192.55.83.30

Explanation: Those are the name server (NS) records for com and the associated address (A) records. The 172800 tells the name server you're using to cache the record for 172,800 seconds (two days). That is called the TTL (time to live).

Simple explanation: The root servers basically said, "I don't know. Here are the name servers of com and their IP addresses. Ask them. You don't have to ask me for the name servers of com for another two days."

The name server you're using now asks the name servers of com for the address (A) record(s) for www.example.com.

The name servers of com will answer:

EXAMPLE.COM.            172800  IN      NS      a.iana-servers.net.
EXAMPLE.COM.            172800  IN      NS      b.iana-servers.net.

a.iana-servers.net.     172800  IN      A       192.0.34.43
b.iana-servers.net.     172800  IN      A       193.0.0.236

Explanation: Those are the name server (NS) records for example.com and the associated address (A) records (which are called glue records). If the name servers of com did not return glue records, the name server you're using would then have to search for the associated address (A) records.

Simple explanation: The name servers of com basically said, "I don't know. Here are the name servers of example.com and their IP addresses. Ask them. You don't have to ask me for the name servers of example.com for another two days."

The name server you're using now asks the name servers of example.com for the address (A) record(s) for www.example.com.

The name servers of example.com will answer:

WWW.EXAMPLE.COM.        172800  IN      A       192.0.34.166

Explanation: That is the address (A) record of www.example.com. The name server you're using now has the address (A) record of www.example.com cached for two days, unless the cache is flushed or the server is restarted and the cache is not saved.

Simple explanation: The name servers of example.com basically said, "I know! It's 192.0.34.166! You don't have to ask me for the address of www.example.com for another two days." The name server you're using now "remembers" the address of www.example.com for two days. If it "forgets," it can just go through the same process again.

If you register a com domain, the name servers of com are the ones that have to update. Since the name servers of com only update twice a day, you will have to wait until your domain is included before it starts working. Your ISP does not update anything. Nothing "spreads throughout the Internet." Information is gathered as needed.

Thanks for the informative post ToastyX
I'm sure there are a lot of people that don't know the basics of DNS.
Very well done.
Perhaps I should have included a copy of the named.ca file to illustrate my point

Cheers!

PS
Location does matter :p

 

[Jeff]

Interesting stuff for sure!
Naturally, I have no idea what you're all talking about. :p

Welcome to Namepros, DaDude.

 

[ToastyX]

Originally posted by CoolHost.com
Interesting stuff for sure!
Naturally, I have no idea what you're all talking about. :p

They are talking about propagation, a myth someone made up to explain why domains take so long to resolve when you register them or why domains take so long to switch name servers when you change them. For some reason, many people believe this myth without understanding how things work, and because so many people believe this myth, nobody believes me when I speak the truth.

Here are the facts once again:

The name servers that delegate com and net domains only update twice a day, and the changes don't usually make it until the update after the next update, so new registrations and name server changes won't take effect for up to 24 hours. The name servers that delegate biz and us domains update every 15 minutes, so new registrations and name server changes will take effect within 15 minutes. Any other delays you experience are due to caching.

- The delay has nothing to do with "propagation." Nothing "spreads throughout the Internet." Information is retrieved on demand.
- If your registrar does real-time updates, as in the changes are submitted to the registry as soon as you make them (which is the case with most automated systems), then the delay has nothing to do with your registrar.
- The delay has nothing to do with your location nor the location of your registrar.
- The delay has nothing to do with your ISP. Your ISP does not update anything. You don't even have to use your ISP's name servers. You can run your own name server or use someone else's.
- http://www.serena1.com/internet_info.html is blatantly false. That document confuses DNS with routing. Routing is not done with DNS.

I'm tired of constantly having to explain only to have nobody believe me. I'm tired of wasting my time. Nobody is paying me to explain, so why should I bother?

 

[Jeff]

Originally posted by ToastyX
I'm tired of constantly having to explain only to have nobody believe me. I'm tired of wasting my time. Nobody is paying me to explain, so why should I bother?

Stay cool, now.
Thank you for your in-depth explanation(s) here, Toasty ... and I do value your thoughts, opinions, and reasoning on the matter here entirely. Much of this information was very useful for me, and no doubt many other Namepros members who came across this excellent, useful thread. No doubt.
My :p statement above was sort of directed at Namecaster, it's an inside joke that I'm not the most knowledgeable "DNS/Propogation" member. LOL.
I don't think you should be frustrated, though ... seems to me your opinions are pretty thoroughly researched and backed-up with real life experience. Again, ALL of the information as presented in this thread has been extremely helpful.
Appreciate it.

 

[NameCaster]

Originally posted by ToastyX

- http://www.serena1.com/internet_info.html is blatantly false. That document confuses DNS with routing. Routing is not done with DNS.

I'm tired of constantly having to explain only to have nobody believe me. I'm tired of wasting my time. Nobody is paying me to explain, so why should I bother?

Perhaps you should take that up with the author?

Personally I feel the same way you do.
It would be a complete waste of our time to continue this thread.

Cheers!

 

[guru]

A .us domain from godaddy propagated in less than five minutes for me, twice!!!

 

[namemarket]

amazingly seconds or minutes to propogate

Actually, with GD/WW, I have had MANY domains propogate within minutes (perhaps seconds) nationwide, from the time I sent the webpage to my server and added the IP address.

Not sure but could possibly be related to the fact I am located only 30 miles frpm WW/Go Daddy's address. Does that make a difference? Anyone know? don't see why it would matter but perhaps it does??

When I put up a site and change an IP at Enom or Tucows (and others) for example, the propogation normally takes 24 to 48-hrs.

All the more reason GoDaddy/Wild West is the best.

 

[Delete]

I regged at rackshack and it was almost instantly

 

[Dave_Z]

Hi everyone!

Is this thread a result of what I asked before? About how a domain resolves to a website and all?

Thanks for the info, everyone. And I apologize if I started something that got everyone so darn hot about.

By the way, assuming the registrar does real time updating (so to speak) and, say, sends .COM & .NET updates every 12 hours, the actual waiting part is how long all the ISPs around the world update their internal cache, right?

In short, registrars give the 24-72 propagation time frame to make sure everyone is updated?

 

[identity_00]

Here is a good article - I think it explains it very well.
I am afraid propagation takes time.

http://www.serena1.com/internet_info.html#propagate

 

[g0ldy]

Originally posted by RealNames
I have had many websites propogate in SECONDS.

How can you?

 

[webscorpion]

I had a few names go for two hours at eNom.

This discussion about propagation, dns, etc... is getting us newbies more confused :?

 

[Dave_Z]

Originally posted by webscorpion
I had a few names go for two hours at eNom.

This discussion about propagation, dns, etc... is getting us newbies more confused :?

Sorry about the confusion. Why not post your questions in a nutshell?

I'm sure most if not all here are more than happy to answer them for you....convincingly. :hehe:

 

[webscorpion]

I'm so confused, I don't even know what to ask

Thanks.