DNS update speed depends in any way on the hosting company?

[Zeokat]

Well... i tested at least three shared hosting companies that advertise here at KWWH.

Two of them are quite fast propagating DNS, in 6 hours i have many DNS updated (http://www.whatsmydns.net/) , but with one of my actual hosters the update is more slow... and can be this issue realted to hosting company?
Why some update DNS faster than others?

Thanks in advance.

Zeokat Reviewed by Zeokat on 1st Mar 2012. DNS update speed depends in any way on the hosting company? Well... i tested at least three shared hosting companies that advertise here at KWWH. Two of them are quite fast propagating DNS, in 6 hours i have many DNS updated (http://www.whatsmydns.net/) , but with one of my actual hosters the update is more slow... and can be this issue realted to hosting company? Why some update DNS faster than others? Thanks in advance. :) Rating: 5

[laucad]

Have you tried lowering the TTL?

[-sky-]

becouse this abut DNS TTL If you need faster Resolve set it small time

[CuraHack]

Also it might be your DNS host, maybe they "reload" the records every hour, therefor creating a longer delay...

[Dj Mad]

Well... i tested at least three shared hosting companies that advertise here at KWWH.

Two of them are quite fast propagating DNS, in 6 hours i have many DNS updated (http://www.whatsmydns.net/) , but with one of my actual hosters the update is more slow... and can be this issue realted to hosting company?
Why some update DNS faster than others?

Thanks in advance.

The hosting companys have nothing to do with dns propagating(once setup properly) ,it is done from different DNS Servers around the world.There are many factors involed in the dns updating world wide,some are time related,some are register time related,etc.


i could explain this more in detail but if you google the MAJOR dns Servers arond the world,its prob explained better.

[okone]

Thats not completely correct Dj Mad.

As people mentioned above, it can also be down to the TTL you set on the records.

Then it is essentially down to your ISP's DNS resolver (or whichever DNS service you use) to update their records. If functioning properly, they should respect the TTL setting of the authoritative name server. Until the TTL runs out, the resolver will not re-cache the record.

[Dj Mad]

Thats not completely correct Dj Mad.

As people mentioned above, it can also be down to the TTL you set on the records.

Then it is essentially down to your ISP's DNS resolver (or whichever DNS service you use) to update their records. If functioning properly, they should respect the TTL setting of the authoritative name server. Until the TTL runs out, the resolver will not re-cache the record.

yea i know thats why i told google it lol

[esson]

do you guys know about ipconfig /renew

[okone]

I think you mean: ipconfig /flushdns

That only flushes your local DNS cache. If your ISP has not updated their DNS when you flush, it won't matter.