DNS

Jake232

New member
Sep 4, 2010
712
4
0
So,

I moved servers around 15 days ago to a new host. My domain was registered with GoDaddy(Shit, I know). I pointed the DNS to the new host and it all worked out fine, everything was running smoothly.

Now, yesterday a client that uses some 'web based software' started telling me that it wasn't working correctly. Anyway, I went on TeamViewer and have narrowed down the problem to that he is still following the old DNS, and is ending up on my old server.

I've tried flushing his DNS and all sorts, but he connects to the old server. Anyone know of a solution, or had this problem before?

I would have thought after 15 days, that the DNS should be fully complete.
 


1: open up cmd type: ipconfig /flushdns

2: check if there isn't anything set under his host file:
http://en.wikipedia.org/wiki/Hosts_(file)

Done both of these.

3: do a traceroute and see how its routed

Not quite sure what any of the results mean anyway, so this isn't helping unfortunately.

I went with GoDaddy (my mistake), and they're giving me the run-around, telling me it's all fine and must be my browser caching things. It isn't, and this is affecting several of my customers, all of which I have personally gone on TeamViewer and cleared their cache.

I'd say its affecting 5% of total visits, does anyone else have any ideas? :(
 
Change their dns servers and see if it makes a difference. Try with Google dns 8.8.8.8,8.8.4.4. IF the site loads properly it a prob with dns.
 
Temp fix (but not a real fix):
If you still have access to the old server, do a 301 or 302 redirect to the new site.

The problem is with whatever it is he's using to connect to your site. It's controlled by the 'web-based service' and the only way around it is to use something else or contact the operators of the service.