Re: Strange bind error
> > For the first time I saw those curious errors. I don't understand where > > is the error, in my bind or in the remote client/server?? > > > > Any idea? > > > > Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: > > Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: > > Invalid argument > > DNS queries with source port 0 could cause this, I suppose. I don't think so. You shouldn't get an error binding to '0' port unless all your resources are used (AFAIK). I think there might be some race condition there, because I've seen similiar errors during peek load. -- Dariush Pietrzak, Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
Re: Strange bind error
> > For the first time I saw those curious errors. I don't understand where > > is the error, in my bind or in the remote client/server?? > > > > Any idea? > > > > Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: > > Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: > > Invalid argument > > DNS queries with source port 0 could cause this, I suppose. I don't think so. You shouldn't get an error binding to '0' port unless all your resources are used (AFAIK). I think there might be some race condition there, because I've seen similiar errors during peek load. -- Dariush Pietrzak, Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange bind error
* Emmanuel Lacour: > For the first time I saw those curious errors. I don't understand where > is the error, in my bind or in the remote client/server?? > > Any idea? > > Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: > Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: > Invalid argument DNS queries with source port 0 could cause this, I suppose. -- Current mail filters: many dial-up/DSL/cable modem hosts, and the following domains: bigpond.com, di-ve.com, fuorissimo.com, hotmail.com, jumpy.it, libero.it, netscape.net, postino.it, simplesnet.pt, spymac.com, tiscali.co.uk, tiscali.cz, tiscali.it, voila.fr, yahoo.com.
Re: Strange bind error
* Emmanuel Lacour: > For the first time I saw those curious errors. I don't understand where > is the error, in my bind or in the remote client/server?? > > Any idea? > > Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: > Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: > Invalid argument DNS queries with source port 0 could cause this, I suppose. -- Current mail filters: many dial-up/DSL/cable modem hosts, and the following domains: bigpond.com, di-ve.com, fuorissimo.com, hotmail.com, jumpy.it, libero.it, netscape.net, postino.it, simplesnet.pt, spymac.com, tiscali.co.uk, tiscali.cz, tiscali.it, voila.fr, yahoo.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange bind error
Hi, I too am getting these strange errors, I've had a quick hunt round the net and can only find references to a relays.monkeys.org but they specify the IP as 244.254.254.254 whereas the IP's i'm getting are completely different. I should note that I dont believe its causing problems for my name servers, just would like to know why its happening!? Gabe May 19 13:45:47 ns0 named[28155]: internal_send: 217.26.199.4#0: Invalid argument Apr 28 02:03:06 ns0 named[28155]: internal_send: 204.49.14.246#0: Invalid argument Apr 28 02:03:06 ns0 named[28155]: internal_send: 204.49.14.246#0: Invalid argument Apr 19 12:31:07 ns0 named[28155]: internal_send: 217.26.199.4#0: Invalid argument Apr 19 12:31:08 ns0 named[28155]: internal_send: 217.26.199.4#0: Invalid argument Apr 19 12:31:08 ns0 named[28155]: internal_send: 217.26.199.4#0: Invalid argument Apr 23 19:27:08 ns0 named[28155]: internal_send: 204.49.14.246#0: Invalid argument On 21 Apr 2004, at 21:11, Emmanuel Lacour wrote: Hi, For the first time I saw those curious errors. I don't understand where is the error, in my bind or in the remote client/server?? Any idea? Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: Invalid argument Apr 21 22:00:50 volubilis named[12517]: client 203.147.0.49#0: error sending response: invalid file Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: Invalid argument Apr 21 22:00:50 volubilis named[12517]: client 203.147.0.49#0: error sending response: invalid file -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange bind error
Hi, I too am getting these strange errors, I've had a quick hunt round the net and can only find references to a relays.monkeys.org but they specify the IP as 244.254.254.254 whereas the IP's i'm getting are completely different. I should note that I dont believe its causing problems for my name servers, just would like to know why its happening!? Gabe May 19 13:45:47 ns0 named[28155]: internal_send: 217.26.199.4#0: Invalid argument Apr 28 02:03:06 ns0 named[28155]: internal_send: 204.49.14.246#0: Invalid argument Apr 28 02:03:06 ns0 named[28155]: internal_send: 204.49.14.246#0: Invalid argument Apr 19 12:31:07 ns0 named[28155]: internal_send: 217.26.199.4#0: Invalid argument Apr 19 12:31:08 ns0 named[28155]: internal_send: 217.26.199.4#0: Invalid argument Apr 19 12:31:08 ns0 named[28155]: internal_send: 217.26.199.4#0: Invalid argument Apr 23 19:27:08 ns0 named[28155]: internal_send: 204.49.14.246#0: Invalid argument On 21 Apr 2004, at 21:11, Emmanuel Lacour wrote: Hi, For the first time I saw those curious errors. I don't understand where is the error, in my bind or in the remote client/server?? Any idea? Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: Invalid argument Apr 21 22:00:50 volubilis named[12517]: client 203.147.0.49#0: error sending response: invalid file Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: Invalid argument Apr 21 22:00:50 volubilis named[12517]: client 203.147.0.49#0: error sending response: invalid file -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Strange bind error
Hi, For the first time I saw those curious errors. I don't understand where is the error, in my bind or in the remote client/server?? Any idea? Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: Invalid argument Apr 21 22:00:50 volubilis named[12517]: client 203.147.0.49#0: error sending response: invalid file Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: Invalid argument Apr 21 22:00:50 volubilis named[12517]: client 203.147.0.49#0: error sending response: invalid file
Strange bind error
Hi, For the first time I saw those curious errors. I don't understand where is the error, in my bind or in the remote client/server?? Any idea? Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: Invalid argument Apr 21 22:00:50 volubilis named[12517]: client 203.147.0.49#0: error sending response: invalid file Apr 21 22:00:50 volubilis named[12517]: socket.c:1100: unexpected error: Apr 21 22:00:50 volubilis named[12517]: internal_send: 203.147.0.49#0: Invalid argument Apr 21 22:00:50 volubilis named[12517]: client 203.147.0.49#0: error sending response: invalid file -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
