Cleared all of my cache but still seeing old website

Question

I have a website setup on a free host called 00webhost. I was previously using a free web host called wink.s. I have a .com domain purchased from 1and1. I had wink.ws's DNS servers pointed to the domain (my .com).

2 days ago I changed the .coms DNS's to the 000webhosts DNS's. For some reason, I still keep seeing the wink.ws one even though my domain isn't pointed to their DNS servers. The thing is, everyone else who accesses the domain can see the new website host (000webhost).

So I figured it was a cache problem. I cleared all my browser cache, ran ccleaner, and flushed DNS in CMD prompt, restarted computer, and still can't get to the new website, it keeps taking me to the old one. I'm honestly out of ideas on what to do.

Solution 1

It may be that the DNS changes haven't yet propagated to the DNS server you are using.

You can try using a different DNS server temporarily until the changes have spread everywhere.

To do this:

• Go to Network Connections in the Control Panel
• Double click on the connection that is being used
• Click Properties
• Double click Internet Protocol Version 4
• Set the new server addresses:

The one I have set in my example is one of Google's DNS servers - 8.8.8.8.

Solution 2

Your browser may no longer be caching the old site, but there could be multiple servers between you and the wider web that are erroneously caching the site.

What IP address to you get if you use PING or NSLOOKUP on that domain name? Old or new?

If you want to cheat and avoid (rather than solve) the problem, you can add an entry to your hosts file, which will force your PC to go to the new server.

Comments

[Garrulinae]

What OS are you using?

[Donavon]

win 7 home prem x64

[Nullpointer42]

Does the problem follow your computer or your internet connection or both? That is, if a friend brought their laptop to your location would they see the issue, or if you took your laptop to a coffee shop, would you still see the issue?

[Nullpointer42]

Note that means anyone on your connection, maybe even on your ISP will have this issue . . . for completeness sake, you should throw a redirect up on your old site . . .

[Nullpointer42]

I was thinking An HTTP redirect to the IP would work, assuming the web server is configured to handle a request via IP . . . if it's a shared server, this may not work, and may just redirect to the hosting companies landing page . . .

[stanley chris]

Works also for js tags and images

[Peregrino69]

Welcome to SuperUser. Please take the quick Toursuperuser.com/tour) to learn how StackExchange Q&A sites differ from internet forums. Please also see Answering- and Asking -sections in the Help to learn how things work. I re-formatted the answer to fit better on the site. The answer could be improved by explaining why and how exactly does this help in the situation. See "How do I write a good answer" in Help for more suggestions From Review