"named" sometimes points people to old locations

Hi there guys,

I've got a problem, and I'm not sure how to fix it.

Situation:

We moved a client's site over from another server to our server, and pointed their domain to our nameservers. Now, over one month after doing this we have the following problem: About 25%-50% of the site requests are getting routed to the old server. I've run traceroutes upon traceroutes, and they're all getting to my server. For some reason, my server is then sending them BACK to the old server. My domain host said this can happen when a nameserver is using an old cache of the names.

How do I fix this? The client is torqued, and I can't blame her, but I'm at a loss as to what I need to do to stop it from happening.

To be honest, I'm not even sure what causes me to need the named service running. Do I need it running if I'm simply running normal shared accounts on the server?

Any help would be greatly appreciated,
json

 

Thanks very much for your reply, and I think it helped me get closer to the problem.

I ran the search tool in the first link you provided, and got these results. Please notice that it shows:

and later:

Avahost is the old server it was hosted on. schwimsdns.com is the new server that it's supposed to be hosted on.

The problem is occuring regardless of the ISP, so I'm pretty sure that the problem lies with the fact that for some reason, my server is sending the requests to avahost.net, but only some of the time.

How do I get my server (schwimsdns.com) to stop pointing requests to the old server (avahost.net)?

The reason I asked about the named service being necessary, is because during setup, it kept asking if I was sure that I wanted it running that it was resource intensive.

thanks very much for taking the time to help me.
json

 

Thanks very much for your reply. I edited the zone file, and it had the old information in it, which I never thought to check since I had created the templates. Not very bright of me.

I changed them and when I run the DNS Reports test, it's now showing correctly, but when I view the site or connect via FTP, I'm still getting to the old site sometimes. I thought that since the change was being made at the final location, that any changes would be immediate. Is this not the case? Do I need to wait the normal 24-48 hours for the ISP's to note that there's no longer any "stealth nameservers"?

Thanks again very much for your help,
json

 

I did as you suggested, and wrote a reply to the bug report. Thanks very much for your assistance. It would have taken me forever to stumble upon it!

thanks,
json