Re: DNS not updated for some
All DNS changes should be planned in advance. Set your timeouts short in advance so that old cached results expire quickly on all real world and local boxes. The cost for the extra DNS traffic is not large. Make the change. When you have ensured all your changes are working the way you want, reset your timeouts on your bind server to their standard long time. If your mail provider does this often, then just run with shorter times in general. If it doesn't happen often, then see why they didn't give you a heads up.
You can force your local hosts that have the wrong DNS information to flush their DNS entries from the command line - you'll have to query the internet for the proper commands for the various operating systems you have.
ADD: Be sure to flush the DNS information in any active directory servers you have as well. I'd start there and then propagate down to the clients. As far as netbios related browsing is concerned, that can also get cached in a different place but I don't remember where.
Last edited by William Haller; 6th March 2012 at 03:25 PM.
Reason: Added active directory.