Why aren't my DNS changes working yet?


Why aren't my DNS changes working yet?

Last updated September 13th, 2010

DNS changes you have applied can take up to 72 hours to take effect, depending on what specifically was changed. Most of the time it will take less than this.

The basic reason behind the delay is that changes to DNS need to 'propagate' and update cached DNS records around the world. This process is outside the direct control of SiteHost.

Can I check the current status of my domain?

One way to check whether you have pointed your domain correctly is to run a 'dig' command for your domain name against one of your domain's nameservers e.g.

dig example.co.nz @ns1.sitehost.co.nz

Tip: Control the DNS Cache

It is possible to apply a level of control to DNS propagation by defining how long DNS servers cache the DNS record for. This is done by defining the TTL (Time-to-live) against the domain's zone file.

By default SiteHost sets the TTL as 3600 - which is 3600 seconds, or 60 minutes. You can drop this all the way down to 60 seconds if required.

Obviously altering the TTL will only help to reduce propagation time if it is implemented well in advance of any changes to the DNS records.

To alter the TTL on a domain's zone:

  1. Log into the SiteHost Control Panel.

  2. Select the "DNS Zones" module from the menu on the left.

  3. Select the domain/zone you want to alter the TTL for.

  4. Click the "Show Advanced" button on the right above the list of DNS records

  5. Alter the TTL. This can be set as low as 60. We recommend you put it back to 3600 when your need for higher refreshes is over.

  6. Click Update records.

Can we improve this article? Suggest an improvement to this article.

Suggest an Improvement

Thank you for helping us to improve this Knowledge Base article. Please type your suggestions below:

Still need help? Get in touch with us.

If you aren't able to find the help you need then please send us a question and we can help you further.