Dns records updating
What I mean by "inconsistent" is the following scenario: Suppose you have an A record for to the IP address 220.127.116.11 with a "Time To Live" value set to 3600 (1 hour).
And let's further assume that you now want to update this A record so that it points to the IP address 18.104.22.168.
The most essential concept to understand in web hosting is the Domain Name System.
At its most basic level, DNS determines whether a visitor to your site sees the actual site, or a “Server not found” error.
For example, you could enter the IP address 22.214.171.124 in your Web browser to reach the Network Solutions®® website, or you could simply enter Understand that DNS updates will take up to 2 hours to take effect (updates may resolve more quickly at some locations than others because many name servers on the Internet retrieve updates at different times).
If you manage your domain's Office 365 records at your DNS hosting provider, you don’t have to worry about the steps in this topic.
Now you can change your NS records so that they point to the new nameserver(s).
If all the DNS records are in place and the site still is unreachable, it’s possible that the DNS changes are propagating.Like a telephone book, DNS matches names (your domain name) to numbers (IP addresses).If your browser returns a “Server not found” error when visiting a new subdomain or a site you’ve recently created (or moved here), it’s likely that a DNS record has either not yet been created or has not yet had sufficient time to propagate.If you are using Liquid Web nameservers, you can add a record for the new subdomain in your Manage interface by clicking on Domains in the left menu and then selecting the DNS tab.The record for a new subdomain would be entered in the main domain’s zone file.
Search for dns records updating:
a resolver who already queried your nameserver 8 minutes ago) would still see the old IP address (126.96.36.199).