DNS Propagation Check on US ISPs

Quick select:

Providers in: India United States United Kingdom

Please wait, we are asking the DNS servers of internet providers in the United States.
Getting ready0 s
  • Please wait
Your IP:
Report generated on
Checked:

What each provider's DNS answers

    Rate this result

    Changed a DNS record? Enter the domain and pick the record type. We ask the DNS servers of Comcast, AT&T and Verizon and other home internet providers in the United States, from inside their own connections, and show which ones already give the new answer, which still give the old one, and when each will switch.

    DNS Propagation Overview

    What is DNS propagation?

    When you change a DNS record, the change is live on your name servers at once. But every internet provider keeps a copy of the old answer in its own DNS servers for as long as the record's TTL allows, so its customers keep getting the old answer until that copy runs out. Propagation is the time it takes for every provider's copy to run out.

    Why check the providers in the United States?

    Most people use the DNS servers of their own internet provider. A worldwide propagation check asks big public DNS services, which tells you little about what customers of Comcast, AT&T and Verizon see. This check asks each provider's own DNS from a test point inside a real home connection on that provider.

    How do I read the results?

    • The blue box shows the correct answer, taken straight from the domain's own name servers.
    • Updated means the provider already gives the correct answer.
    • Old answer means the provider still gives a different answer. The time shown is how long it still keeps that answer, and the clock time is when it should switch.
    • No answer means the provider's DNS did not reply this time. Run the check again in a few minutes.
    • A grey DNS label such as Google DNS means the owner of that test point uses a public DNS service instead of the provider's own DNS.

    Checking again while you wait is the normal way to use this page: each run shows how many providers have switched so far.

    FAQs

    Each provider's DNS servers keep an answer for as long as the record's TTL allows. A provider that asked just before your change keeps the old answer until that time runs out, while a provider that asks after the change gets the new one straight away.

    At most the TTL that was set on the old record, counted from the moment each provider last asked for it. This check shows the time each provider still keeps its answer and the clock time it should switch.

    No. A worldwide check asks big public DNS services in many countries. This check asks the DNS servers of home internet providers in the United States, from inside their own connections, which is what their customers actually use.

    The owner of that test point set it to use a public DNS service such as Google DNS or Cloudflare DNS instead of the provider's own DNS. That answer shows the public service. Most customers of the provider use the provider's own DNS.

    Lower the TTL of the record a day before you change it, for example to 5 minutes. Providers then keep the old answer for only a few minutes after the change. Raise the TTL again once the change is done.

    Propagation problems and practical fixes

    Its DNS servers asked for the record just before you changed it, and the old record had a long TTL, such as one day.

    How to fix: Wait until the time shown for that provider runs out. Next time, lower the TTL to 5 minutes a day before the change, then raise it again afterwards.

    The change may not be on the name servers that are actually in charge of the domain, for example when the record was changed at a DNS host the domain no longer uses.

    How to fix: Compare the correct answer in the blue box with what you entered. If the blue box shows the old value, make the change at the DNS host named in the NS records of the domain.

    That provider's DNS timed out or refused the question this time, which happens now and then on busy servers.

    How to fix: Run the check again in a few minutes. If the same provider never answers for your domain only, check that every name server of the domain answers.

    Sites that use a content delivery network answer with the server nearest to each visitor, so different providers get different addresses on purpose.

    How to fix: Nothing to fix. The result marks this case when the domain keeps answers for only a few minutes.