I have updated my DNS settings. Now how long will it take before my domain starts resolving?

When DNS records have been changed it takes about 24 hours for the changes to propagate and take effect. Only after that you will be able to see the result of the DNS changes you have made.

If after 24 hours the DNS change has not taken effect yet, try clearing your browser's cache.

To resolve a domain name to a certain IP address without having to wait for the DNS change to propagate, you can modify your hosts file.

Important! When you change the nameservers of a domain, all advanced records (A-records, CNAME-records, MX-records, SRV-records and so on) would resolve from the DNS zone of the provider, whose nameservers you are setting. Thus, if you are using a custom A-record or MX-record for your needs, it is strongly recommended to add them in the DNS zone of your new provider in order to ensure minimal downtime and / or propagation.


  1. Reply May 6, 2015 / 20:45 AndreSiteGround Team

    Yes, but wordpress admin doesn't work

    • Reply May 7, 2015 / 05:28 Hristo PandjarovSiteGround Team

      I am positive that's a completely different issues. If you have DNS problems your entire site will either work or not, not just different parts of it.

  2. Reply July 6, 2015 / 06:26 Lynne JoySiteGround Team

    Hi Hristo,
    I need to change the nameservers at Dotster, registrar for thewateradvocate.org, so that my website can be hosted by siteground. What is the dns address for siteground or the information I have to give to Dotster to allow siteground to host my domain thewateradvocate.org?

    I need to be up and running by July 8, 2015.
    Thank you.

    • Reply July 6, 2015 / 07:39 Hristo PandjarovSiteGround Team

      They are different for each server. You can get yours from the left column in your cPanel, they start with n1. and n2s.

  3. Reply July 13, 2015 / 05:12 JamesSiteGround Team

    I just changed the nameservers for a domain registered at go daddy so siteground can host it, how long before it shows up on the my account page in siteground?

    • Reply July 13, 2015 / 12:27 Hristo PandjarovSiteGround Team

      Usually, the propagation period ends in 24 hours.

  4. Reply September 24, 2015 / 14:09 Osundare ToheebSiteGround Team

    Pls I Have Issue With 1and1, I Bought Domain From Them 3days Ago And Is Yet To Be Activated, Pls What Can I Do??

    • Reply September 28, 2015 / 16:06 Marina YordanovaSiteGround Team

      Hello, it would be best to contact 1and1 directly and ask them for assistance. They will be able to give you information about the status of the registration and clarify if there are issues with it.

  5. Reply May 2, 2016 / 08:10 Gianpiero GagliassoSiteGround Team

    I add the new dns to a new domain and it seem ok but when i do a refresh of the setting page the dns files are empty. Why?

    • Reply May 3, 2016 / 10:46 escalationsSiteGround Team

      If this is a new domain name purchased by us, please post a ticket in our HelpDesk, explaining the issue as detailed as possible and our technical support team will assist you with resolving the problem.

      In case the domain name has not been purchased by us, then it is the support team of the domain provider to which you should address the issue.

  6. Reply September 24, 2016 / 20:37 PaulSiteGround Team

    I've just signed up and will transfer over an existing domain (carmela.co.uk). I have updated the name servers. Whist I wait for the name servers to propagate, is there a temp URL or IP address I could use to see and work on the website?

    • Reply October 4, 2016 / 12:52 Ivan StefanovSiteGround Team

      Paul, you can always use the temporary server URL by typing the server main IP address, "~" and your cPanel username -> IP.IP.IP.IP/~username for example

      • Reply October 26, 2016 / 16:51 mcchuckerSiteGround Team

        When i move to another server, Before i do the move i go to my advanced dns settings and change the TTL values to the lowest value. Normally on most servers this is about an hour. Then i wait a day for remote servers to gather only an hour of cached information. I then change the nameservers to point to the new server at my domain registry. Almost always this results in no downtime whatsoever and no waiting for your domain to solve to the new host. This also works if you are just pointing your A record to another server and not changing nameservers, but if this is the case you must go back to your advanced settings and change the TTL's to their original value after your website populates to the new host.

        • Reply October 27, 2016 / 08:55 Ivan StefanovSiteGround Team

          Thank you for the feedback. We fully agree that in most of the cases this is a good scenario.

      • Reply March 24, 2017 / 13:52 CosmeSiteGround Team

        Hi Ivan,

        I'm a new user and when I try to access via IP.IP.IP.IP/~username it redirects me to the live website. What am I doing wrong?


        • Reply March 29, 2017 / 13:56 Ivan AtanasovSiteGround Team


          It is likely that the application in your public_html folder is domain dependant (such as WordPress). Meaning, it will work for the domain it is configured with.

          When you use the temporary URL to access the website, the application loads and redirects you to the domain name.

  7. Reply January 23, 2017 / 07:58 Elia BeduschiSiteGround Team

    If I transfer a domain on monday, can I keep the old dns till the weekend for dont have the email blackout

    • Reply January 31, 2017 / 15:54 Ivan StefanovSiteGround Team

      Elia, there is no problem to keep the old nameservers until you are completely prepared for the site and mails migration.

  8. Reply February 28, 2017 / 07:34 SOHAMSiteGround Team

    Hi I just changed my nameservers that were given by cloudflare now it is giving me this error DNS_PROBE_FINISHED_NXDOMAIN.
    What do I do ?

    • Reply February 28, 2017 / 12:50 Ivan AtanasovSiteGround Team

      Hello Soham,
      As explained by this article, the NameServers modification is not instant and will take time to propagate globally and take effect.

      The error message you are receiving in your browser is because the DNS loopkup your browser uses is failing. Once the propagation reaches your location, it should work correctly.
      You can also try clearing your local DNS cache.

* (Required)