socket.c:2135: unexpected error:

[hotta at iij.ad.jp]

On Tue, 5 Jun 2018 12:48:53 -0400
Bob Harold <rharolde at umich.edu> wrote:

> On Mon, Jun 4, 2018 at 10:57 PM <hotta at iij.ad.jp> wrote:
> 
> >
> > Hi,
> >
> > After upgrading BIND from 9.9.9-P5 to 9.11.3., the following messages
> > have been displayed continuously in the file /var/log/messages as below.
> >
> > ---------
> > May 29 02:36:50 dns01 nanny[5609]: debug start 1
> > May 29 02:37:08 dns01 named[1679]: socket.c:2135: unexpected error:
> > May 29 02:37:08 dns01 named[1679]: internal_send: [global IPv6
> > address]#38306: Invalid argument
> > May 29 02:37:20 dns01 nanny[5617]: debug start 1
> > May 29 02:37:24 dns01 named[1679]: socket.c:2135: unexpected error:
> > May 29 02:37:24 dns01 named[1679]: internal_send: [global IPv6
> > address]#36987: Invalid argument
> > May 29 02:37:47 dns01 named[1679]: socket.c:2135: unexpected error:
> > May 29 02:37:47 dns01 named[1679]: internal_send: [global IPv6
> > address]#35862: Invalid argument
> > May 29 02:37:48 dns01 named[1679]: socket.c:2135: unexpected error:
> > May 29 02:37:48 dns01 named[1679]: internal_send: [global IPv6
> > address]#39895: Invalid argument
> > May 29 02:37:50 dns01 nanny[5632]: debug start 1
> > May 29 02:38:00 dns01 named[1679]: socket.c:2135: unexpected error:
> > May 29 02:38:00 dns01 named[1679]: internal_send: [global IPv6
> > address]#38979: Invalid argument
> > :
> > ---------
> >
> > OS  : Red Hat Enterprise Linux Server 6.5
> >
> > DNS service seems to be working fine, but I don't understand the cause
> > and how to fix the errors.
> >
> > Any advice would be greatly appreciated.
> >
> >
> > Regards,
> > Hotta
> >
> 
> Just guessing, but it sounds like " [global IPv6 address]" is either
> malformed, or it is expecting an IPv4 address.
> 
> -- 
> Bob Harold

Thank you for advice.
[global IPv6 address] looks like the right address.
We did not know the cause of errors, so returned to the previous version
on the production environment.
After that we have tried various tests in our IPv6 testing environment,
but it works fine without the same errors.

--
Hotta