DNS Propagation -
The way your browser gets to an internet website is through the Domain Name System, otherwise known as DNS. The reason you may not be able to see a DNS change (such as name server changes, or updating an A Record) is because of “DNS Propagation”. Unfortunately the Domain Name System is not perfect, and it does require time for updates because of its dynamic nature. Thankfully this system is dynamic otherwise you would never be able to change where your domain name pointed, and if you did, no one else would be able to see it.

All of your website lookups (for example going to google.com in firefox) are looked up through your Internet Service Provider’s “DNS Resolver”. The DNS resolver is managed by them (your ISP) so you don’t have to. Your computer will connect to the DNS resolver they manage to check where a domain name points. If it is in the DNS cache they store on that server it will direct to that IP address and show you the website which is located on that IP address. However if the domain name is NOT listed in that cache they keep the DNS resolver will go and see where that domain name points. The process is as follows;
1. Your ISP’s DNS resolver will check the root servers to see where it needs to check for your domain name, this changes based on the the TLD (top level domain, ie. .com .net .org .biz)
2. Once it determines who the registrar is authoritative for the TLD, it then looks up via the Registrar (where the domain was purchased) what the name servers are. In this example the name servers will be ns1.bluehost.com and ns2.bluehost.com
3. During the DNS process here the name servers show everything about the domain name. The DNS resolver server is looking for the zone file. The zone file is a file that is located on the name servers that tells what the Arecords, Cnames, MX entries etc. are for the domain name you have looked up.
4. Now your ISP’s DNS resolver knows everything about that domain name, it basically copies the information from the name servers ns1.bluehost.com and ns2.bluehost.com.
5. The DNS resolver will cache this information it receives from ns1.bluehost.com and ns2.bluehost.com (generally for 4 – 24 hours). They do this so when their other customers go to the website it wont have to lookup the domain name again. However when people using a different ISP go to lookup the domain name they wont have this information so their ISP will have to do the same lookup and then cache the information likewise. That is exactly why your domain name can be working in some places and not working / showing the old site in other places.

If your ISP’s DNS resolver server already has the domains information it will bring you right to the domain name. Even though you may have made changes to your domain name through your DNS zone editor. Your ISP wont know that you made changes until the TTL(Time To Live) is expired for the domain name (generally 4 -24 hours). Then the DNS will be looked up again to obtain that change you made.