On 11/12/2012 04:15 PM, Andrew Sullivan wrote:
> On Mon, Nov 12, 2012 at 04:05:37PM -0500, Christopher Browne wrote:
>> Is it possible that your libc is doing cacheing?  If *that's* the
>> case, and I'm suspicious of it, then you really would need to restart
>> the slon to get "unstuck" from what libc has cached on you...
> 
> More likely, the system resolver is pointing at a caching name server.

Thanks for prompt answers, everyone.

I'll pursue this as an issue with our use of Ubuntu on Amazon/EC2.

   Mark