This is a discussion on RE: named crash within the Bind Users forums, part of the DNS and Related Forums category; Two ways to solve: 1) change the port to 953 in named.conf file 2) if in UNIX then make ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
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 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 |
![]() |
| Thread Tools | |
| Display Modes | |
|
|