[159626] in North American Network Operators' Group
Re: Intermittent incorrect DNS resolution?
daemon@ATHENA.MIT.EDU (Erik Levinson)
Wed Jan 16 17:33:03 2013
Date: Wed, 16 Jan 2013 17:26:43 -0500
From: Erik Levinson <erik.levinson@uberflip.com>
To: RijilV <rijilv@riji.lv>
In-Reply-To: <CAAycvn3QZTxjZ-AEv6mNXQG4ELLNf10iUUb8Ve_6O+xx1TF2dQ@mail.gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Good point.
While I haven't checked the distribution of source IPs yet, I briefly
grepped for the User-Agent headers in the tcpdump output, and there's a
higher than expected bot presence, particularly Baidu.
That said, there are also "normal" UAs (whatever that means, with every
device/software pretending to be something else these days).
On 16/01/13 05:20 PM, RijilV wrote:
> Also client programs don't always honor TTLs either. For example, JAVA
> defaults to ignoring TTLs and holding IPs forever.
>
> *networkaddress.cache.ttl (default: -1)*
> Indicates the caching policy for successful name lookups from the name
> service. The value is specified as as integer to indicate the number of
> seconds to cache the successful lookup. A value of -1 indicates "cache
> forever".
>
> Depending on who your clients are, your milage may vary.
>
> .r'
>
