Maintained by: NLnet Labs

[Unbound-users] SOLVED: Re: sendto failed: Invalid argument

Toni Mueller
Sat Jun 30 21:56:18 CEST 2012


On Fri, May 25, 2012 at 08:43:38PM -0700, David Benfell wrote:
> You wrote:
> > May 25 19:01:16 atlanta unbound: [31267:0] notice: sendto failed: 
> > Invalid argument May 25 19:01:16 atlanta unbound: [31267:0] notice:
> > remote address is 208.67.220.220 port 53
> > 
> > I'm assuming this stems from my attempt to implement dnscrypt
> > (which seemed fairly disastrous even after I got the other problem
> > solved). I've tried backing out those changes, but I'm now unable
> > to find the web page where I found the directions which I
> > followed.
> > 
> 
> Well, I'm actually balding and greying (from black), but I guess this
> is what some people call a "blonde" moment:
> 
> > outgoing-interface: 127.0.0.1

I have a real IP in there, but still get these

May 26 11:46:54 debian unbound: [18205:0] notice: sendto failed: Invalid argument
May 26 11:46:54 debian unbound: [18205:0] notice: remote address is 80.236.108.223 port 0

Jun 10 16:40:57 debian unbound: [18205:0] notice: sendto failed: Invalid argument
Jun 10 16:40:57 debian unbound: [18205:0] notice: remote address is 67.215.13.106 port 0

and these

Jun 14 02:35:14 debian unbound: [18205:0] notice: sendto failed: Resource temporarily unavailable
Jun 14 02:35:14 debian unbound: [18205:0] notice: remote address is 64.40.8.45 port 25345

I'm on 1.4.16 atm.


If someone could share tips about what to do, that would be nice!


Kind regards,
--Toni++