NamePros
Welcome, Guest! Ready to make a name for yourself in the domain business? We welcome both the hobbyist and professional domainer to join the discussion as part of the NamePros community.

Click here to create your profile to start earning reputation for posting, and trader ratings for buying & selling in our free e-marketplace. Build your trader rating with each successful sale. Our system has tracked over 100,000 sales and counting!
FAQ & TOS Register Search Today's Posts Mark Forums Read

Go Back   NamePros.com > Domain Name Discussion Forums > Domain Names > Domain Name Discussion
Reload this Page What's the quickest a domain name has propagated for you?

Domain Name Discussion The place for general domain name related discussions.

Advanced Search


Closed Thread
Page 1 of 3 1 23
 
LinkBack Thread Tools
Old 08-08-2003, 11:50 AM THREAD STARTER               #1 (permalink)
NamePros Member
Join Date: Jul 2003
Posts: 63
N9ne is an unknown quantity at this point
 

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

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?
N9ne is offline  
Old 08-08-2003, 01:05 PM   #2 (permalink)
Retired Staff
 
NameCaster's Avatar
Join Date: May 2003
Location: Seattle
Posts: 1,963
NameCaster has a spectacular aura aboutNameCaster has a spectacular aura about
 
I've had them propagate within 2 hours using godaddy or enom.
NameCaster is offline  
Old 08-08-2003, 01:26 PM   #3 (permalink)
NamePros Regular
Join Date: Jun 2003
Posts: 678
carmonle is just really nicecarmonle is just really nicecarmonle is just really nicecarmonle is just really nicecarmonle is just really nice
 
For me around 18 hours (im located in Israel)

Eran
__________________
http://www.cafewiz.com/Isomac_Millenium.htm
carmonle is offline  
Old 08-08-2003, 02:09 PM THREAD STARTER               #4 (permalink)
NamePros Member
Join Date: Jul 2003
Posts: 63
N9ne is an unknown quantity at this point
 
Quote:
Originally posted by NameCaster
I've had them propagate within 2 hours using godaddy or enom.
2 Hours?! That's got to be a record...
N9ne is offline  
Old 08-08-2003, 05:05 PM   #5 (permalink)
Senior Member
 
darksk8er's Avatar
Join Date: Jun 2003
Location: Oregon
Posts: 1,606
darksk8er is a jewel in the roughdarksk8er is a jewel in the roughdarksk8er is a jewel in the rough
 
6 hours at namecheap

Lowest - 36 hours eNom
__________________
http://www.HiDefinition.net
HiDefinition Web Solutions.
David Gomez | CEO
darksk8er is offline  
Old 08-08-2003, 10:44 PM   #6 (permalink)
NamePros Member
Join Date: Jun 2003
Posts: 45
Exsitense is an unknown quantity at this point
 
Mine was 10 hours and the domain was re gistered at godaddy.com.
Exsitense is offline  
Old 08-09-2003, 08:18 AM   #7 (permalink)
Senior Member
 
Webtwink's Avatar
Join Date: Jul 2003
Location: United States of America
Posts: 1,158
Webtwink is a glorious beacon of lightWebtwink is a glorious beacon of lightWebtwink is a glorious beacon of lightWebtwink is a glorious beacon of lightWebtwink is a glorious beacon of lightWebtwink is a glorious beacon of lightWebtwink is a glorious beacon of lightWebtwink is a glorious beacon of light
 

Domain Propagating

"I've had them propagate within 2 hours using godaddy or enom"


What does that mean? You mean domain resolving?
Last edited by Webtwink; 08-09-2003 at 10:47 AM.
Webtwink is offline  
Old 08-09-2003, 10:24 AM   #8 (permalink)
Kirsten
Guest
Posts: n/a
 
About 4 hours at godaddy.
 
Old 08-09-2003, 11:21 AM   #9 (permalink)
New Member
Join Date: Aug 2003
Posts: 7
ToastyX is an unknown quantity at this point
 
Domains don't "propagate." The time it takes for your domain to start resolving has nothing to do with "propagation," nor does it have anything to do with your registrar or your location. I don't understand where people get this from.
ToastyX is offline  
Old 08-09-2003, 12:01 PM   #10 (permalink)
dax
Senior Member
 
dax's Avatar
Join Date: Jun 2003
Location: .Net
Posts: 1,363
dax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud of
 
Quote:
Originally posted by ToastyX
...nor does it have anything to do with your registrar or your location...
Yes, i agree with ToastyX.
It depends on ISP, not the registrar!
__________________
Prometheus.net
Last edited by dax; 08-10-2003 at 05:13 AM.
dax is offline  
Old 08-09-2003, 12:50 PM   #11 (permalink)
New Member
Join Date: Aug 2003
Posts: 7
ToastyX is an unknown quantity at this point
 
NO! It has nothing to do with your ISP either!
ToastyX is offline  
Old 08-09-2003, 12:58 PM   #12 (permalink)
dax
Senior Member
 
dax's Avatar
Join Date: Jun 2003
Location: .Net
Posts: 1,363
dax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud of
 
Ok, if you know so much, tell us
__________________
Prometheus.net
dax is offline  
Old 08-09-2003, 01:12 PM   #13 (permalink)
Retired Staff
 
NameCaster's Avatar
Join Date: May 2003
Location: Seattle
Posts: 1,963
NameCaster has a spectacular aura aboutNameCaster has a spectacular aura about
 
Quote:
Originally posted by ToastyX
Domains don't "propagate." The time it takes for your domain to start resolving has nothing to do with "propagation," nor does it have anything to do with your registrar or your location. I don't understand where people get this from.
Perhaps resolving would be a better choice of terms.
But in fact domains DO propagate although technically its the root DNS files that are propagating.

Location does matter. Zone files aren't all updated at the same time. This all depends on the TTL setting in the DNS files.
JMHO


Here is a good read for newbies:
http://www.serena1.com/internet_info.html



Useful links:
http://www.dnsreport.com
????: NamePros.com http://www.namepros.com/domain-name-discussion/4329-whats-quickest-domain-name-has-propagated.html

http://www.dnsstuff.com

http://www.domainwhitepages.com
NameCaster is offline  
Old 08-09-2003, 01:13 PM   #14 (permalink)
Retired Staff
 
NameCaster's Avatar
Join Date: May 2003
Location: Seattle
Posts: 1,963
NameCaster has a spectacular aura aboutNameCaster has a spectacular aura about
 
Quote:
Originally posted by ToastyX
NO! It has nothing to do with your ISP either!

????: NamePros.com http://www.namepros.com/showthread.php?t=4329

I would have to disagree with that comment
NameCaster is offline  
Old 08-09-2003, 01:41 PM   #15 (permalink)
dax
Senior Member
 
dax's Avatar
Join Date: Jun 2003
Location: .Net
Posts: 1,363
dax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud of
 
Quote:
Originally posted by NameCaster


I would have to disagree with that comment
Let me explain:
I think ToastyX is refering to inside-registry distribution system
- from Master nameserver to slave nameservers (which ISPs use for resolving a domain name)
Quote:
The zone file is a flat database file consisting of the technical information that the DNS requires to function correctly: the domain name, nameserver hostname, and IP addresses (as necessary). Traditionally, a TLD registry would update the zone file by generating a completely new zone file. This zone file would be propagated to the nameservers, and would write over the existing zone file. The size of the zone file and the fact that it was a complete replacement for the existing zone file dictated that the process be done infrequently, resulting in a process that could update zone files at most once or twice a day
__________________
Prometheus.net
dax is offline  
Old 08-09-2003, 03:08 PM   #16 (permalink)
New Member
Join Date: Aug 2003
Posts: 7
ToastyX is an unknown quantity at this point
 
Quote:
Originally posted by NameCaster
Perhaps resolving would be a better choice of terms.
But in fact domains DO propagate although technically its the root DNS files that are propagating.

Location does matter. Zone files aren't all updated at the same time. This all depends on the TTL setting in the DNS files.
JMHO


Here is a good read for newbies:
http://www.serena1.com/internet_info.html


Newbies, PLEASE do NOT read that. That is NOT how DNS works! Where do people get this stuff?

I don't have time to explain how it all works, but the reason "com" and "net" domains take so long to resolve after you register them is because the name servers that delegate "com" and "net" domains only update twice a day. If you register a "us" domain, it will "propagate" much faster because the name servers that delegate "us" domains update every 15 minutes. That has nothing to do with your registrar unless your registrar doesn't do real-time updates. That has nothing to do with your location. That has nothing to do with your ISP. Your ISP doesn't update anything.
ToastyX is offline  
Old 08-09-2003, 04:18 PM   #17 (permalink)
Retired Staff
 
NameCaster's Avatar
Join Date: May 2003
Location: Seattle
Posts: 1,963
NameCaster has a spectacular aura aboutNameCaster has a spectacular aura about
 
Quote:
Originally posted by ToastyX
????: NamePros.com http://www.namepros.com/showthread.php?t=4329


Newbies, PLEASE do NOT read that. That is NOT how DNS works! Where do people get this stuff?

I don't have time to explain how it all works, but the reason "com" and "net" domains take so long to resolve after you register them is because the name servers that delegate "com" and "net" domains only update twice a day. If you register a "us" domain, it will "propagate" much faster because the name servers that delegate "us" domains update every 15 minutes. That has nothing to do with your registrar unless your registrar doesn't do real-time updates. That has nothing to do with your location. That has nothing to do with your ISP. Your ISP doesn't update anything.
You seem to have an attitude problem?
You mean I've been doing DNS wrong all this time
I've been maintaining servers in the ISP field for 8+ years both Linux and Windoze so I like to think I know a little bit about how DNS works.

I realize that the root servers are updated several times a day.
But from my experience they don't all update simultaneously.
Therefore location can be a factor on the time the domain fully propogates. Yes, thats what I said DOMAIN PROPOGATES.
Isn't that why they say it usually takes 24-72 hours?

So before you go making me look like I don't know what the phuck I'm talking about do a little research yourself Mr Know-it-All!

I like how you show up with guns a blazin telling people they are wrong but "don't have time to explain how it all works" or at least provide resources for the basis of your rigid spew.

BTW
Welcome to NamePros
Cheers!
NameCaster is offline  
Old 08-09-2003, 06:20 PM   #18 (permalink)
New Member
Join Date: Aug 2003
Posts: 7
ToastyX is an unknown quantity at this point
 
Quote:
Originally posted by NameCaster
You seem to have an attitude problem?
How would you feel if no matter where you went, people claimed the Earth is flat and provided scientific documents explaining how the Earth is flat even though you knew for a fact the Earth is round? This is very frustrating for me. Some things may come off the wrong way because you can't hear the tone of my voice, but I assure you, I'm not trying to be rude.
????: NamePros.com http://www.namepros.com/showthread.php?t=4329

You gave a link to a document that is blatantly false. Domains don't propagate like that document claims. That's exactly what I mean when I say domains don't propagate.
Quote:
I've been maintaining servers in the ISP field for 8+ years both Linux and Windoze so I like to think I know a little bit about how DNS works.
Experience does not equate to knowledge.
Quote:
So before you go making me look like I don't know what the phuck I'm talking about do a little research yourself Mr Know-it-All!
You're the one making me look like I don't know what I'm talking about. I'm a know-it-all for speaking the truth?
Quote:
I like how you show up with guns a blazin telling people they are wrong but "don't have time to explain how it all works" or at least provide resources for the basis of your rigid spew.
I don't have time to write a document on how DNS works. I shouldn't have to go out of my way to prove how something works when you can find out for yourself.
????: NamePros.com http://www.namepros.com/showthread.php?t=4329
Quote:
BTW
Welcome to NamePros
Thanks.
ToastyX is offline  
Old 08-10-2003, 05:01 AM   #19 (permalink)
dax
Senior Member
 
dax's Avatar
Join Date: Jun 2003
Location: .Net
Posts: 1,363
dax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud ofdax has much to be proud of
 
Quote:
Originally posted by ToastyX
Your ISP doesn't update anything.
I am sorry, but you are wrong.
ISP updates EVERY DAY the list of IP locations where the TLD nameservers for each gTLD and ccTLD can be found.
Since there are about 200 ccTLDs and around 10 gTLDs, ISP has to have IP location for each gTLD and ccTLD nameserver.
When it has correct ns IP, it communicates with the particular nameserver (fe .com ns) in order to get SLD IP location. -> this is called "resolving".
Quote:
Originally posted by ToastyX
You're the one making me look like I don't know what I'm talking about.
I don't have time to write a document on how DNS works.
Well, it seems that you are making yourself look like don't know what you are talking about.
You do not understand the difference between RESOLVING and PROPAGATION.

Propagation is the way that DNS records spread throughout the Internet , from Registry (master ns to the slave nameservers) to the ISPs.
Resolving, on the other hand, is something that Internet is based on. You use resolving every time you surf, mail etc. Resolving is basically converting domain names into IP addresses!.

It is that simple.
And saying you don't have time to write something that simple, maybe is just an excuse to make yourself clever, while not knowing much about it.
__________________
Prometheus.net
Last edited by dax; 08-10-2003 at 05:17 AM.
dax is offline  
Old 08-10-2003, 05:43 AM   #20 (permalink)
Senior Member
Join Date: Jul 2003
Location: UK
Posts: 3,923
Matt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud of
 

Approved Contest Holder Approved Contest Holder

I've had one go in about 2.5hrs

The lonest I remmber is about 48+ with sy4.com (although i think that was cause of crapness from the previous domain holders.
__________________
Gamerz.Biz - Possibly For Sale
Matt is offline  
Old 08-10-2003, 07:07 AM   #21 (permalink)
Senior Member
 
darksk8er's Avatar
Join Date: Jun 2003
Location: Oregon
Posts: 1,606
darksk8er is a jewel in the roughdarksk8er is a jewel in the roughdarksk8er is a jewel in the rough
 
GamerDesign took 45 Hours before people stop seeing SY4.net
__________________
http://www.HiDefinition.net
HiDefinition Web Solutions.
David Gomez | CEO
darksk8er is offline  
Old 08-10-2003, 07:54 AM   #22 (permalink)
Senior Member
Join Date: Jul 2003
Location: UK
Posts: 3,923
Matt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud ofMatt has much to be proud of
 

Approved Contest Holder Approved Contest Holder

lol
__________________
Gamerz.Biz - Possibly For Sale
Matt is offline  
Old 08-10-2003, 12:49 PM   #23 (permalink)
New Member
Join Date: Aug 2003
Posts: 7
ToastyX is an unknown quantity at this point
 
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:

Code:
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.
????: NamePros.com http://www.namepros.com/showthread.php?t=4329

The root servers will answer:

Code:
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.
????: NamePros.com http://www.namepros.com/showthread.php?t=4329

The name servers of com will answer:

Code:
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:

Code:
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.
ToastyX is offline  
Old 08-10-2003, 06:02 PM   #24 (permalink)
New Member
Join Date: Aug 2003
Location: Florida
Posts: 7
DaDude is an unknown quantity at this point
 
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.
DaDude is offline  
Old 08-10-2003, 09:18 PM   #25 (permalink)
NamePros Regular
 
David G's Avatar
Join Date: May 2003
Posts: 265
David G is on a distinguished road
 
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!
David G is offline  
Closed Thread
Page 1 of 3 1 23

« Google Page Rank Updated | Audiobooks dot net »

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools


Liquid Web Smart Servers  
All times are GMT -7. The time now is 01:21 PM.

Contact Us - NamePros.com - Privacy Statement - Top
Managed Web Hosting by Liquid Web
Domain name forum recommended by Domaining.com Powered by: vBulletin® Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.6.0 Ad Management plugin by RedTyger