Why BIND is throwing Error "socket.c:5268: unexpected error" ?

Solution Verified - Updated -

Issue

  • Why BIND is throwing the Error
  Mar 31 15:54:22 hostname named[1056]: socket.c:5268: unexpected error:
  Mar 31 15:54:22 hostname named[1056]: connect(fe80::#53) 22/Invalid argument

Environment

  • Red Hat Enterprise Linux 6.5
  • bind-9.8.2-0.17.rc1.el6_4.6.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In