DNS Caching Problem (TTL Issue) - Any DNS gurus want to comment?

[PeteC]

I have a new customer. His last host gave him a nameserver, ns1.hisdomain.com. Apparently the host created a DNS zone for him and the "www" record had a huge TTL on it.

He's moved to our service, registered the nameservers we gave him, changed the nameservers on his domain, and allowed everything to propagate. Now everything works except that www.hisdomain.com still reports the old IP address if you use a caching nameserver. This is still the case a week later.

One more detail I will add is that he asked for ns2/ns3.hisdomain.com when he signed up with is. I don't know if modifying ns1.hisdomain.com to use our IP address will help update all the nameserver caches.

He says his old ISP is not helpful, and they do not have his old IP assigned so it's not possible to get an authoritative lookup on www.hisdomain.com or to put a more reasonable zone file up.

I wonder if any of you DNS gurus might be willing to shed any light on the situation. I'll tell you his domain name by e-mail or PM, but I don't think I should post it here as I don't have his permission to do so.

Thanks in advance for any insight or help.

[sawbuck]

Okay send a PM so we can look at it. Will post the solution here in the forum if we arrive at one.