[Bug 1804542] Re: Multiple intermittent socket failures during name resolutions

2019-01-23 Thread Andreas Hasenack
Thanks for the pointers. I agree we should try to backport this. ** Changed in: bind9 (Ubuntu) Status: Incomplete => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => Medium ** Tags added: server-next -- You received this bug notification because you are a member of

[Bug 1804542] Re: Multiple intermittent socket failures during name resolutions

2019-01-23 Thread Andreas Hasenack
Thanks for the pointers. I agree we should try to backport this. ** Changed in: bind9 (Ubuntu) Status: Incomplete => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => Medium ** Tags added: server-next -- You received this bug notification because you are a member of

[Bug 1804542] Re: Multiple intermittent socket failures during name resolutions

2019-01-23 Thread Roberto S. Galende
I do also have this problem: 23-Jan-2019 10:20:25.869 general: error: ../../../../lib/isc/unix/socket.c:2135: unexpected error: 23-Jan-2019 10:20:25.869 general: error: internal_send: ***.***.***.***#52218: Invalid argument 23-Jan-2019 10:20:25.869 client: warning: client @0x7f08800da560

[Bug 1804542] Re: Multiple intermittent socket failures during name resolutions

2018-12-27 Thread Jon Schewe
I too am seeing this problem. This is on a computer that I'm using as a router using NAT. I have a dual stack IPv6 setup. My ISP gives me an IPv6 subnet that I use for my internal network. I have attached my configuration files. I received no errors with this configuration under Ubuntu 16.04,

[Bug 1804542] Re: Multiple intermittent socket failures during name resolutions

2018-11-22 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem,