DNS Propagation Checker FAQ
About DNSPropagation.netDNSPropagation.net is a free online tool that helps you to instantly perform a DNS lookup against domain names current IP addresses. It will get your DNS record information against different and multiple name servers around the world. This name servers will show you the result of the dns propagation test.
What is DNS Propagation?
It is the time for all ISPs (internet service providers) from all across the globe to update their DNS cache records to know / detect that the IP has changed for your domain.
As DNS Propagation is done gradually from place to place, some users may see your website responding from the old IP, while other users from different geographic places may see the website responding from the new server. This is totally normal.
When do I need to run this DNS Propagation test?DNS propagation check is useful when you switched webhost or stared a new website and you just changed your domain DNS Name Servers from your domain registrar. This tool will perform a free dns lookup against your IP address and will confirm if the website is completely propagated worldwide or not.
How much time do DNS changes takes to be reflected?It demends on the type of change you made to your DNS.
Name Server changes can take up to 72 hours max to be reflected and fully propated around the world.
DNS record changes are way faster, and can be propagated within a few hours from almost all providers.
Why does it take up to 72 hours?Because it's the way the DNS system was built in first place. It is not an anomally or an error, it is just the way it works. Let's see this with a day to day example:
Your office is located in Miami, US and you just changed the NameServers of your domain that is hosted in a server located in Amsterdam, Netherlands.
When you try to browser your domain in Google Chrome or Mozilla Firefox, the request is not going to be direct to your server, first it has to go trough a few ISP points / nodes. That's is when your notebook / pc starts checking on your local DNS Cache and the request is sent to your Miami ISP.
After that, it is redirected to Chicago, US, and then your request has to cross the Atlantic ocean all over to Europe, to connect to other intermediate ISPs in Spain, until it finally reaches your server located in Netherlands, as you see in the next image:
Each of the mentioned ISPs in the different geographic places check their own DNS Cache to see if they already have information about your domain, if it's not, then they look for it and saves it for next time to avoid requests the next time, this accelerates DNS resolution and traffic over the dns servers.
ISPs also handle the time to live (cache refresh time) differently, that's also another reason on why some of them will discover your new IP soon than others.
Now you know why your dns propagation time takes up to 72 hours.
How can I speed up dns propagation?There are ways to speed up dns propagation, the first one is to use a good provider like the ones mentioned before.
The other thing you can do to improve dns propagation time is to set your DNS zone TTL really low.
When you migrate your website and make dns changes you want the DNS switchover to happen as fast as possible.
You can switch your current TTL and reduce the time before you peform the migration. 600 (10 minutes) is a good TTL value, you must do it at least 24 hours before the migration. 10 minutes before making the change, you can set it even lower, to 60 (1 minute).
This configuration has been proved to work well to accelerate dns propagation.
After all your traffic is served from the new server, you can switch back the TTL to the normal value.
How can I check my DNS Propagation locally from my computer network?
On Unix / Linux you can use dig, for example:
- [webtech@localhost ~]$ dig A dnspropagation.net
- ; <<>> DiG 9.10.4-P6-RedHat-9.10.4-4.P6.fc25 <<>> A dnspropagation.net
- ;; global options: +cmd
- ;; Got answer:
- ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9533
- ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
- ;; OPT PSEUDOSECTION:
- ; EDNS: version: 0, flags:; udp: 512
- ;; QUESTION SECTION:
- ;dnspropagation.net. IN A
- ;; ANSWER SECTION:
- dnspropagation.net. 299 IN A 184.108.40.206
- ;; Query time: 203 msec
- ;; SERVER: 220.127.116.11#53(18.104.22.168)
- ;; WHEN: Thu Mar 23 09:10:15 UYT 2017
- ;; MSG SIZE rcvd: 63
- [webtech@localhost ~]$
You can also use ping command to get your site IP:
- [webtech@localhost ~]$ ping dnspropagation.net
- PING dnspropagation.net (22.214.171.124) 56(84) bytes of data.
- 64 bytes from dnspropagation.net (126.96.36.199): icmp_seq=1 ttl=49 time=174 ms
- 64 bytes from dnspropagation.net (188.8.131.52): icmp_seq=2 ttl=49 time=175 ms
- 64 bytes from dnspropagation.net (184.108.40.206): icmp_seq=3 ttl=49 time=175 ms
- --- dnspropagation.net ping statistics ---
- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms
- rtt min/avg/max/mdev = 174.695/174.952/175.129/0.185 ms
- [webtech@localhost ~]$
For Windows users, you can also use the same ping command and also nslookup:
- C:\> nslookup dnspropagation.net
- Server: 220.127.116.11
- Address: 18.104.22.168#53
- Non-authoritative answer:
- Name: dnspropagation.net
- Address: 22.214.171.124
As you see, in this case the DNS response address is: 126.96.36.199
What are the fastest DNS Providers in the World?