I'm over my head with a DNS issue with W2K. I'm helping a small business change their third party e-mail provider; I made the changes to MX records and CNAME records on Saturday night using the public website hosting company's DNS configuration tool. Within a few hours everything was working just fine from my office: nslookup and ping tests all pointed to the new e-mail servers, and I successfully configured MS Outlook to send/receive some test messages. But this morning the client arrived at his office, and he couldn't access the new mail servers from there. Ping tests from his office showed that his DNS was still mapping mail.theirdomain.com to the old mail server, now 36 hours after the zone records had been updated. I'm thinking that the problem is something about his local W2K network DNS not receiving or not accepting the DNS updates that should have propagated everywhere by now. I don't have any experience with troubleshooting server DNS settings, I am thinking I need to find a way to force his local DNS to refresh itself, but would appreciate it if someone could give me a few pointers to make sure I'm headed in the right direction.