Subject: Re: resolver problems in -current?
To: None <firstname.lastname@example.org>
From: Soren Jacobsen <email@example.com>
Date: 10/09/2003 12:52:37
On 10/09 18:42, Toru TAKAMIZU wrote:
> On Wed, Oct 08, 2003 at 11:39:15PM -0400,
> Sean Davis <firstname.lastname@example.org> wrote:
> > Has anybody else noticed resolver problems in -current? I just updated
> > today, and once the new userland was installed, things like nslookup worked,
> > but the plain libc resolver routines stopped working. the error from
> > gethostbyname corresponted to NO_RECOVERY. Backing up to a userland from
> > september 19th, with a kernel from today, brought everything back to the
> > working state they were in before. I haven't done much digging, so does
> > anybody know the root cause of this? Or better yet, how to fix it?
> Take a look at a thread of current-users titled
> "recent 1-6 branch libc and mozilla (etc.)", though I don't know
> yours is the same problem.
I was seeing the same behavior as Sean, and the problem is the same as
that mentioned in the 1-6 thread. All is fine when I use my ISP's
nameserver instead of a local dnscache. Sean was using dnscache too, I