Ahhh, (i see say the blind man as he tripped over is cane and saw) ;-) You issue isnt really sql at all, nor is it dns so much. You are a victim of one of MS's better TCP/IP stack designs (no really, it is a better design). MS did a great thing is the use of caches when it does its network lookups, it ALWAYS looks at the cache first. Simply flushing the DNS cache won't get rid of your issue, you need to tell those clients not to keep that info cached for so long. You can first try to stop your dnscache doing a net stop dnscache and then try to recreate your problem. You need your dns client running though so you will need to hack the registry of the client and set down the maxpositive TTL and maxmegtive TTL (time to live) values. Default for positive is like a day (measured in seconds) and default value for negative reponse is 15 mins. All that can be found here http://support.microsoft.com/kb/318803
Good luck! ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
