[150597] in North American Network Operators' Group
Re: dns and software, was Re: Reliable Cloud host ?
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Feb 28 04:36:14 2012
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20120228054527.2CF7B1DDE9D8@drugs.dv.isc.org>
Date: Tue, 28 Feb 2012 01:32:17 -0800
To: Mark Andrews <marka@isc.org>
Cc: Nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Feb 27, 2012, at 9:45 PM, Mark Andrews wrote:
>=20
> getaddrinfo was designed to be extensible as was struct
> addrinfo. Part of the problem with TTL is not data sources
> used by getaddrinfo have TTL information. Additionally for
> many uses you want to reconnect to the same server rather
> than the same name. Note there is nothing to prevent a
> getaddrinfo implementation maintaining its own cache though
> if I was implementing such a cache I would have a flag to
> to force a refresh.
>=20
Sorry if I wasn't clear... My point to Bill was that we should be using =
calls that don't have TTL information
(GAI/GNI in their default forms). That we don't need to abuse connect() =
to achieve that. That if people use GAI/GNI(), then, any brokenness is =
system-wide brokenness in the system's resolver library and should be =
addressed there.
Owen
