What is the standard DNS propagation period?

Categories Domain NamesDNS Tags dnszone records

Before trying to understand DNS propagation, it is recommended you understand the Domain Name System (DNS). When the name servers or zone records a domain name uses are modified, it can take several hours for all the computer systems around the world to recognise all the changes that have been made. This time period is known as DNS propagation. This delay occurs for several reasons and is not completely in our control.

Internet Service Provider (ISP) cache

In order to speed up the internet browsing experience for their customers, each Internet Server Provider (ISP) caches (stores) DNS records. This means that after a customer of a particular ISP views your website or sends you an email, the ISP keeps a record of what name servers your domain name were delegated to and what zone records existed on those name servers. When a new customer from the same ISP attempts to view your website or email you, the ISP will find the cached record that it saved locally on their system instead of looking up the records on the Internet. This saves time and provides the user a much faster internet browsing experience.

The problem is that if you make a change to the name servers or zone records used with your domain name, an ISP may not notice these changes until a few hours later. In the time between your changes taking place and the ISP updating their servers, the ISPs customers will continue to follow the old cached copy of your records.

This delay and use of cached records can cause some visitors to see your old website while others see your new website. It can also mean that some emails are sent to your old email server while others are sent to your new server. As soon as the cache at all the ISPs servers are updated, all records fall back into sync and all visitors are taken to the same place.

Time To Live (TTL)

The TTL is the time period that the zone file tells other servers to cache zone records for. By setting the TTL to a shorter time period, users can shorten the propagation time for their DNS changes to be noticeable. However, shortening the TTL increases the number of requests sent to the DNS server and increases load and processing time.

We allow users to modify and set the TTL for zone records that they add into the their zone file. But we don't let you modify the TTL for zone records which we place into your zone file by default.

Modifying a zone records TTL and then modifying the actual record right away will not increase the propagation time of your DNS changes. The new TTL needs to be cached at the ISP prior to the DNS change in order for you to take advantage of the shorter TTL. If you wish to speed up DNS propagation for your own personal zone records, it is recommended that you modify the TTL to a shorter time period many hours prior to actually modifying the DNS records.

In some cases, ISPs ignore the TTL settings and update their cached records every two to three days so setting the TTL to a short time period does not always guarantee quicker propagation.

How long does propagation take?

Propagation will depend on your approximate location to the domains Name Server.  If you are connecting to a domain registered by us and are:

  • Within Australia = 2 hours
  • Outside Australia = 4 hours
  • New domains regardless of location = 6 hours

Due to advances in technology, however, some ISP’s can refresh within 20 minutes. But you should expect up to four hours for most people to find your domain online.

I’m making changes to my website content.  How long before that becomes available?

Changes made to a website content are not affected by DNS propagation because, provided the DNS information is correct, the registry information will show a correct pathway to the hosting server where the website content is stored. Any delay in displaying updated content on your website is therefore controlled by the application cache and occasionally ISP cache. Hold down the left shift key and click the Refresh button on your browser to clear the local application cache and reload the website content.

Rate this article