- Admin
- #1
- Messages
- 40
- Reaction score
- 27
- Points
- 37
When we migrate a website from one server to another it is very common for our hosting provider to tell us something like that we have to wait for the DNS propagation time for us to see our site from the new server.
This is quite normal and it is because the IP change in DNS records takes up to 72 hours maximum to spread throughout the world, through each ISP in each country.
There are many ways to verify DNS propagation when we make changes to our website at the DNS record level.
One of the more traditional ways of doing it is using the famous command dig that is present in Linux and Unix:
For example:
Or for an MX record for example:
Also if we use the ping command, it is possible to know how some type A record responds, example:
On Windows you can also use the nslookup command, as seen below:
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, whether we use ping or dig.
There are also several more automated ways to check how DNS propagation responds from different parts of the world.
Using DNS checking tools, it is possible to know massively and in just a few seconds how a certain type of DNS records responds from different countries on different continents.
As you can see, either using a manual method from your local network or using automated tools, DNS records can be obtained without a problem.
This is quite normal and it is because the IP change in DNS records takes up to 72 hours maximum to spread throughout the world, through each ISP in each country.
There are many ways to verify DNS propagation when we make changes to our website at the DNS record level.
One of the more traditional ways of doing it is using the famous command dig that is present in Linux and Unix:
For example:
You don't have permission to view the spoiler content.
Log in or register now.
Or for an MX record for example:
You don't have permission to view the spoiler content.
Log in or register now.
Also if we use the ping command, it is possible to know how some type A record responds, example:
You don't have permission to view the spoiler content.
Log in or register now.
On Windows you can also use the nslookup command, as seen below:
You don't have permission to view the spoiler content.
Log in or register now.
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, whether we use ping or dig.
There are also several more automated ways to check how DNS propagation responds from different parts of the world.
You don't have permission to view the spoiler content.
Log in or register now.
Using DNS checking tools, it is possible to know massively and in just a few seconds how a certain type of DNS records responds from different countries on different continents.
As you can see, either using a manual method from your local network or using automated tools, DNS records can be obtained without a problem.
