How to Verify DNS Propagation

When we migrate a website from one server to another it is very common for our hosting provider to tell us something like we have to wait for the DNS spread so that we can see our site from the new server.

This is quite normal and it is because the change of IP in DNS records takes up to 72 hours maximum to spread around the world, through each ISP in each country.

There are several ways to check DNS propagation when we make changes to our website at the DNS record level.

One of the most traditional ways to do this is to use the famous deployment command on Linux and Unix:

for example

digging A hostingdiario.com
Or for an MX record for example:

digging MX hostingtoday.com
Additionally, if we use the ping command, you can find out how to respond to a type A record, for example:

ping hostingdiario.com
In Windows, you can also use the nslookup command, as shown below:

nslookup.tusitio.com
Server: 192.168.2.1
Address: 192.168.2.1
One of the disadvantages of this method is that it only serves to verify how a DNS record responds from a single location, that is, from your local network through your ISP, ping or digging.

There are also several other automated ways to check how the spread of DNS responds from different parts of the world.

By using DNS control tools like DNS Propagation you can know massively and in seconds as it responds to certain types of DNS records from different countries on different continents.

As you see, using a manual method from your local network, or using automated tools can get DNS records without problems.

Comentarios