RE: named crash

bind-users-bounce@isc.org wrote on 07/22/2004 08:40:21 AM:
> Two ways to solve:
>
> 1) change the port to 953 in named.conf file
>
> 2) if in UNIX then make this change in you /etc/services file
> domain 953/udp
>
> domain 953/tcp

Yes, this will change the port that BIND listens on, however, how will the
rest of the world know to talk to your implementation of BIND that is
running on port 953. The rest of the DNS speaking world is looking for
name resolution on port 53. Your server may stay up, although I don't see
why changing the port would solve the problem, but, no one would be able
to talk to it. Either way, staying up and running on the wrong port or
crashed, the result is the same, no name resolution.


Unfortunately, I have never seen the errors stated by the OP, so, I can't
offer any other solution. I think someone else will pipe in though.


hth,

Dave...


>
> Zakaria
>
>
> -----Original Message-----
> From: list3@wwwcrazy.com [mailto:list3@wwwcrazy.com]
> Sent: Thursday, July 22, 2004 8:37 AM
> To: bind-users@isc.org
> Subject: named crash
>
>
> 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
>