named crash

[Sten Carlsen]

I see this sometimes, mostly when my ISP decides that I can no longer 
have my IP(fixed IP, using DHCP), then the network drops on that port 
and any attempt to send on that interface gives basically the same error.

I suggest you concentrate on the log to see what happened to network 
connectivity just before that line.

list3 at wwwcrazy.com wrote:

>Anyone know what the problem may be with this machine.
>
>Running Bind 9.2.3
>
>Here are the last few lines of the log and then all of a sudden poof!  It
>stops working.
>
>Jul 21 22:49:17 tune named[10221]: socket.c:1111: unexpected error:
>Jul 21 22:49:17 tune named[10221]: internal_send: 64.127.107.3#53: Invalid
>argument
>Jul 21 22:49:17 tune named[10221]: socket.c:1111: unexpected error:
>Jul 21 22:49:17 tune named[10221]: internal_send: 38.113.1.32#53: Invalid
>argument
>
>  
>

-- 
Best regards

Sten Carlsen

Let HIM who has an empty INBOX send the first mail.