> Machine A is trying to access a filesystem on machine B via amd +
> nfs. Machine A first looks up machine B's AAAA record, this fails and
> then it looks up machine B's A record. This succeeds and the file
> accesses go through.
>
> However, when Machine B's named goes to lunch (this is the named that
> machine A is using), the query for the AAAA record times out and then
> the query for A happens some 30-45 seconds later and succeeds right
> away.
>
> At least that's my reading of the tcpdump traffic.
>
> None of these machines should be using IPv6 since we have no IPv6
> machines and don't use IPv6 address. No AAAA records are defined at
> all. And it only seems to happen sometimes. I don't know what kills
> named in the first place, just what happens when it goes partially
> brain dead.
>
> Warner
Ah, that will be same problem with others and it is not named
problem but resolver problem, I think.
Could you please try applying my patches to the 4.0 machine?
Thanks,
Yoshinobu Inoue
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
