[32457] in Kerberos

home help back first fref pref prev next nref lref last post

Re: bug report: "too many SRV records" becomes "no SRV records"

daemon@ATHENA.MIT.EDU (Richard Silverman)
Thu Jun 10 16:58:25 2010

Date: Thu, 10 Jun 2010 16:54:05 -0400 (EDT)
From: Richard Silverman <res@qoxp.net>
To: Tom Yu <tlyu@mit.edu>
In-Reply-To: <ldvtypbt4md.fsf@cathode-dark-space.mit.edu>
Message-ID: <Pine.LNX.4.64.1006101649300.31938@seraph.oankali.net>
MIME-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu

On Thu, 10 Jun 2010, Tom Yu wrote:

> "Richard E. Silverman" <res@qoxp.net> writes:
>
>> In 1.8.1, there is the following code in src/lib/krb5/os/dnsglue.c:
>>
>>    krb5int_dns_init(struct krb5int_dns_state **dsp,
>>                     char *host, int nclass, int ntype)
>>    {
>>    ...
>>      nextincr = 2048;
>>      maxincr = INT_MAX;
>>    ...
>>
>> One day, due to an error, the number of KDC SRV records for one of our
>> realms doubled from 27 to 54... and KDC lookups via DNS prompty broke.  I
>> bumped up the nextincr value above, and it started working again.
>> Probably not the right fix, but just letting you know that there's a bug
>> here.
>
> What platform/OS is this on?  A "too-large" response should result in
> res_nsearch() returning the actual size.  If it's returning -1
> instead, I can see it causing trouble.  Are you willing to run stuff
> under a debugger to see what res_nsearch() actually returns there?

Oh: it's Solaris 10 / x86.
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post