For Sale Enjoying Rapid DNS yet?

[seeker]

mudi, you'd need to transfer them and pay a fee.

 

[mike031]

i registered a bunch of names over at enom just earlier today... typed them into my browser immidiately after my order was confirmed and 2 sec's later they were online, resolving just fine... not sure with other registrars but enom seems to be working just fine!

 

[ToastyX]

Every time I see people talk about DNS, they get confused.

When you register a new domain or change the name servers for a domain, several things happen. First, the registrar has to submit the change to the registry. For most registrars, such as eNom and GoDaddy, this happens within seconds if nothing goes wrong. The next thing that happens is you have to wait for the registry (VeriSign for .com and .net domains) to update their name servers. VeriSign used to update their name servers only twice a day, and changes didn't make it until the update after the next update, so you had to wait 12-24 hours for changes to take place. This is what they changed. The name servers now update around twice a minute. After this happens, there is still one more thing to consider. DNS records are looked up on demand (only when requested) and then cached for a length of time specified by the name server. This is called the TTL (time to live). VeriSign has always used and still continues to use a TTL of 2 days for name server records, so if you're changing the name servers for a domain, the DNS servers you're using (most likely your ISP's) might still have the old name servers cached. Windows also maintains its own DNS cache. This is the delay most of you are experiencing. You won't see the change until the cache expires.

 

[seeker]

anyway to override windows's own dns cache?
apparently clearing cache memory of the browser doesnt work.

 

[ToastyX]

You can flush the local DNS cache that Windows maintains, but it won't make a difference if the DNS servers you're using still have the old name servers cached. It doesn't hurt to try though.

To flush the local DNS cache, open a command prompt and enter the following command:

ipconfig /flushdns

If that doesn't help, all you can do is try using a different DNS server (you could run your own if you wanted) or just wait for the cache to expire. Clearing the browser's cache won't have any effect.

 

[mole]

since you're such a smartass, let me explain it in terms a smartass might understand.

any more sarcastic posts you gonna pull out of that sleeve?
Luc L.

Yes, I think you should drop that "moderator" post of yours given your stellar PR skills.

 

[ezimedia]

HI

What extension was the domain.... a .com or .net or what...

Thanks
Tom Dahne

 

[David G]

my dns changes from all my regsitrars take a minimum of 24 hours, usually 48 hours, and sometimes 72 hours. Where is this fast update?

It seems to depend on the quality of the registrar. Some 2nd rate ones appear to not really be operating their Control Panels in real-time but I suspect delayed needing human action to process changes. That is why at many firms no changes are made over the weekend but happen on Mon or Tues instead.

I had a new website online and resolving on the web all within about 1-hr or so of reg'ing the dot-com. Probably would have been only minutes from adding the NS's but took an hour to set up the name on the server and do the temp page.

 

[seeker]

the thing is, I am now wondering who is to blame.
It is true, I see enom's DNS somewhat resolve faster, like 48 hours instead of 72..
But, since I am relaying on my local ISP, how could I ever measure that?
Maybe its my ISP thats late picking them up?

 

[David G]

the thing is, I am now wondering who is to blame. It is true, I see enom's DNS somewhat resolve faster, like 48 hours instead of 72. But, since I am relaying on my local ISP, how could I ever measure that? Maybe its my ISP thats late picking them up?

IMO likely due to the registrar delaying processing the change. Even BEFORE rapid DNS many of my com names resolved very quickly, often a few hrs or even shorter. Very rarely more than 24-hrs. Plus org's have been resolving right away for some time, also well before rapid dns.

 

[stevey]

how long do .co.uk domains take to resolve?

 

[seeker]

you know what. You are right.
.orgs always resolved faster.
So, its not PIR.ORG doing it, becayse why would my ISP pickup orgs faster and not other ones...
food for thought...

- about co.uk's not sure.
The question is, is it the registry or the ISPs.
Its a little fuzzy at the moment.
I wonder if it ever will be clear... as I wonder about the clarity of many other things

 

[MediaHound]

Now I see what you guys are talking about.
New domains propogate virtually instantly for me.

This is very good news for those of us in the domain / website business.

 

[jdk]

yes but my ISP takes 2-3 days before they update on their end...time to find a new ISP

 

[MediaHound]

Hey, something must have changed since I posted that.
It isn't instant for me anymore!
Maybe my ISP, or some other uplink provider, is doing something different.
Did something happen that someone knows about?

 

[stevey]

still working fast for me, got 2 domains update almost instantly today

 

[seeker]

is there a way to locate which ISP's around the world update faster than others and at which times???

No matter what I do, it takes 48 hours for me!

 

[stevey]

have you tried phoning your isp and asking them if they could clear there dns cache more often?

 

[seeker]

actually, I havent.
But I doubt that would help.

 

[stevey]

worth a try, worst they can say is no, and if they say ok and sort it for you saves you messing about getting a new isp