From describes the following two conclusions:
When will take longer than the time zone TTL from the old NS-domain servers, DNS-server ISP address the root servers top-level domain, find the address of the new NS-servers for a domain, refer to the new NS-servers and updates the information about the migrated domain.
Dissemination of information about changes in the Internet domain (also called “domain zone update”) – this is an asynchronous and uncontrolled process: its speed depends on the settings of the previous NS-domain servers and DNS-servers status of each particular ISP. Accordingly, this process can not be controlled, and it is impossible to accurately predict the time of its completion.
Thus, instead of resentment and accusations of a new hosting provider to which you are transferring your domain, it is wise to be patient after the change of the list of NS-domain servers, but better – follow the recommendations listed below to reduce idle time of your domain.
For clarity, the process of redelegation domain can be compared to the procedure already mentioned replacement passport.
That’s no longer a young man comes to the passport office (panel registriratora) and apply for a replacement passport (for redelegation domain). Then he waits a while until checked his data. If everything is correct, he is given a new passport, and data on the new passport “spread” in the various registries government organizations. Of course, it takes some amount of time and, in contrast to the previous example, is often accompanied by all sorts of organizational overlays: somewhere information can not change where things will change, but very nebystro, etc.
As a result, the owner of a new passport, arriving at the bank for a loan, even a month after the change of passports, runs the risk of failure, since the information about his new passport at the branch may be missing. And the man did have to wait for “cache refresh” – retry after information about his new passport will get to the bank in the prescribed manner.