Bind9 socket.c unexpected error
The named process is giving this kind of error the whole day:
Jun 17 12:50:43 s named[24479]: socket.c:5274: unexpected error:
Jun 17 12:50:43 s named[24479]: connect(198.41.0.4#53) 22/Invalid argument
What is this error?
Named (BIND 9.8.4-rpz2+rl005.12-P1) runs on Debian GNU/Linux squeeze/sid x32. From machine I can telnet to this address (a.root-servers.net.), also I can resolve IP address to name with nslookup
debian bind
edited Mar 3 '18 at 20:08
Rui F Ribeiro
40.1k1479136
asked Jun 17 '16 at 9:52
gedOgedO
1065
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 6 more comments
The named process is giving this kind of error the whole day:
Jun 17 12:50:43 s named[24479]: socket.c:5274: unexpected error:
Jun 17 12:50:43 s named[24479]: connect(198.41.0.4#53) 22/Invalid argument
What is this error?
Named (BIND 9.8.4-rpz2+rl005.12-P1) runs on Debian GNU/Linux squeeze/sid x32. From machine I can telnet to this address (a.root-servers.net.), also I can resolve IP address to name with nslookup
debian bind
edited Mar 3 '18 at 20:08
Rui F Ribeiro
40.1k1479136
asked Jun 17 '16 at 9:52
gedOgedO
1065
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Hi welcome to slashdot. Add Linux version/software versions to this post and any future posts please. It seems BIND was unable to connect to that IP. Could be a transient error. Is it your BIND configured for IPv6 only or is the IPv4 interface down? Have you allowed besides UDP/53, TCP/53, if using firewall rules? Test 198.41.0.4 with a dig/nslookup from the BIND machine
– Rui F Ribeiro
Jun 17 '16 at 10:30
Have you restarted named?
– Rui F Ribeiro
Jun 17 '16 at 10:46
Several times, same problem
– gedO
Jun 17 '16 at 10:47
what doessudo tcpdump -nvvv host 198.41.0.4says? leave it running until you have a couple of answers.
– Rui F Ribeiro
Jun 20 '16 at 13:12
Tcpdump captures: pastebin.com/77cLNBk4
– gedO
Jun 20 '16 at 13:27
|
show 6 more comments
The named process is giving this kind of error the whole day:
Jun 17 12:50:43 s named[24479]: socket.c:5274: unexpected error:
Jun 17 12:50:43 s named[24479]: connect(198.41.0.4#53) 22/Invalid argument
What is this error?
Named (BIND 9.8.4-rpz2+rl005.12-P1) runs on Debian GNU/Linux squeeze/sid x32. From machine I can telnet to this address (a.root-servers.net.), also I can resolve IP address to name with nslookup
debian bind
edited Mar 3 '18 at 20:08
Rui F Ribeiro
40.1k1479136
asked Jun 17 '16 at 9:52
gedOgedO
1065
The named process is giving this kind of error the whole day:
Jun 17 12:50:43 s named[24479]: socket.c:5274: unexpected error:
Jun 17 12:50:43 s named[24479]: connect(198.41.0.4#53) 22/Invalid argument
What is this error?
Named (BIND 9.8.4-rpz2+rl005.12-P1) runs on Debian GNU/Linux squeeze/sid x32. From machine I can telnet to this address (a.root-servers.net.), also I can resolve IP address to name with nslookup
debian bind
debian bind
edited Mar 3 '18 at 20:08
Rui F Ribeiro
40.1k1479136
asked Jun 17 '16 at 9:52
gedOgedO
1065
edited Mar 3 '18 at 20:08
Rui F Ribeiro
40.1k1479136
asked Jun 17 '16 at 9:52
gedOgedO
1065
edited Mar 3 '18 at 20:08
Rui F Ribeiro
40.1k1479136
edited Mar 3 '18 at 20:08
Rui F Ribeiro
40.1k1479136
edited Mar 3 '18 at 20:08
Rui F Ribeiro
40.1k1479136
40.1k1479136
asked Jun 17 '16 at 9:52
gedOgedO
1065
asked Jun 17 '16 at 9:52
gedOgedO
1065
asked Jun 17 '16 at 9:52
gedOgedO
1065
1065
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Hi welcome to slashdot. Add Linux version/software versions to this post and any future posts please. It seems BIND was unable to connect to that IP. Could be a transient error. Is it your BIND configured for IPv6 only or is the IPv4 interface down? Have you allowed besides UDP/53, TCP/53, if using firewall rules? Test 198.41.0.4 with a dig/nslookup from the BIND machine
– Rui F Ribeiro
Jun 17 '16 at 10:30
Have you restarted named?
– Rui F Ribeiro
Jun 17 '16 at 10:46
Several times, same problem
– gedO
Jun 17 '16 at 10:47
what doessudo tcpdump -nvvv host 198.41.0.4says? leave it running until you have a couple of answers.
– Rui F Ribeiro
Jun 20 '16 at 13:12
Tcpdump captures: pastebin.com/77cLNBk4
– gedO
Jun 20 '16 at 13:27
|
show 6 more comments
Hi welcome to slashdot. Add Linux version/software versions to this post and any future posts please. It seems BIND was unable to connect to that IP. Could be a transient error. Is it your BIND configured for IPv6 only or is the IPv4 interface down? Have you allowed besides UDP/53, TCP/53, if using firewall rules? Test 198.41.0.4 with a dig/nslookup from the BIND machine
– Rui F Ribeiro
Jun 17 '16 at 10:30
Have you restarted named?
– Rui F Ribeiro
Jun 17 '16 at 10:46
Several times, same problem
– gedO
Jun 17 '16 at 10:47
what doessudo tcpdump -nvvv host 198.41.0.4says? leave it running until you have a couple of answers.
– Rui F Ribeiro
Jun 20 '16 at 13:12
Tcpdump captures: pastebin.com/77cLNBk4
– gedO
Jun 20 '16 at 13:27
Hi welcome to slashdot. Add Linux version/software versions to this post and any future posts please. It seems BIND was unable to connect to that IP. Could be a transient error. Is it your BIND configured for IPv6 only or is the IPv4 interface down? Have you allowed besides UDP/53, TCP/53, if using firewall rules? Test 198.41.0.4 with a dig/nslookup from the BIND machine
– Rui F Ribeiro
Jun 17 '16 at 10:30
Hi welcome to slashdot. Add Linux version/software versions to this post and any future posts please. It seems BIND was unable to connect to that IP. Could be a transient error. Is it your BIND configured for IPv6 only or is the IPv4 interface down? Have you allowed besides UDP/53, TCP/53, if using firewall rules? Test 198.41.0.4 with a dig/nslookup from the BIND machine
– Rui F Ribeiro
Jun 17 '16 at 10:30
Have you restarted named?
– Rui F Ribeiro
Jun 17 '16 at 10:46
Have you restarted named?
– Rui F Ribeiro
Jun 17 '16 at 10:46
Several times, same problem
– gedO
Jun 17 '16 at 10:47
Several times, same problem
– gedO
Jun 17 '16 at 10:47
what does
sudo tcpdump -nvvv host 198.41.0.4 says? leave it running until you have a couple of answers.– Rui F Ribeiro
Jun 20 '16 at 13:12
what does
sudo tcpdump -nvvv host 198.41.0.4 says? leave it running until you have a couple of answers.– Rui F Ribeiro
Jun 20 '16 at 13:12
Tcpdump captures: pastebin.com/77cLNBk4
– gedO
Jun 20 '16 at 13:27
Tcpdump captures: pastebin.com/77cLNBk4
– gedO
Jun 20 '16 at 13:27
|
show 6 more comments
1 Answer
1
active
oldest
votes
I would bet on a transient error, however if the command tools work, and you have this error something is amiss. Maybe a BIND bug, maybe some firewall configuration (inspectors)
Your OS and BIND are quite old and EOL (2013 since it is the testing branch).
I would upgrade both urgently; if you have not kernels and BIND compiled by hand, they have already a couple nasty bugs that can be explored remotely.
If the issue continues to be present, then I would debug further on the problem.
answered Jun 17 '16 at 10:49
Rui F RibeiroRui F Ribeiro
40.1k1479136
1
Thank you. I will upgrade distribution and bind ant let you know
– gedO
Jun 17 '16 at 10:51
This weekend I have upgraded system from Debian 6 to Debian 7. Bind installed version 1:9.8.4.dfsg.P1-6+nm, but still getting same error.
– gedO
Jun 20 '16 at 12:14
Interesting. While we did not deleted the hints about your servers, it seemed to me I could connect to your powerdns server, but not your BIND server from the outside. A chance is also increasing the debug level of BIND, or increasing monitoring in some other way. Do you have firewalls in the way to outside, PIXes or ASAs? Why not Debian 8? I am running it here.
– Rui F Ribeiro
Jun 20 '16 at 12:41
Yes, I have two DNS servers, one BIND ant second PowerDNS. ip route get shows that to that IP address I go over public IP address, so no firewall is in the way
– gedO
Jun 20 '16 at 12:47
Having a route of public IP addresses is no guarantee there are no firewalls, however I do trust you know better about your setup. I am a little busy right now, will came back later with ideas for debugging.
– Rui F Ribeiro
Jun 20 '16 at 12:49
|
show 2 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f290363%2fbind9-socket-c-unexpected-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I would bet on a transient error, however if the command tools work, and you have this error something is amiss. Maybe a BIND bug, maybe some firewall configuration (inspectors)
Your OS and BIND are quite old and EOL (2013 since it is the testing branch).
I would upgrade both urgently; if you have not kernels and BIND compiled by hand, they have already a couple nasty bugs that can be explored remotely.
If the issue continues to be present, then I would debug further on the problem.
answered Jun 17 '16 at 10:49
Rui F RibeiroRui F Ribeiro
40.1k1479136
1
Thank you. I will upgrade distribution and bind ant let you know
– gedO
Jun 17 '16 at 10:51
This weekend I have upgraded system from Debian 6 to Debian 7. Bind installed version 1:9.8.4.dfsg.P1-6+nm, but still getting same error.
– gedO
Jun 20 '16 at 12:14
Interesting. While we did not deleted the hints about your servers, it seemed to me I could connect to your powerdns server, but not your BIND server from the outside. A chance is also increasing the debug level of BIND, or increasing monitoring in some other way. Do you have firewalls in the way to outside, PIXes or ASAs? Why not Debian 8? I am running it here.
– Rui F Ribeiro
Jun 20 '16 at 12:41
Yes, I have two DNS servers, one BIND ant second PowerDNS. ip route get shows that to that IP address I go over public IP address, so no firewall is in the way
– gedO
Jun 20 '16 at 12:47
Having a route of public IP addresses is no guarantee there are no firewalls, however I do trust you know better about your setup. I am a little busy right now, will came back later with ideas for debugging.
– Rui F Ribeiro
Jun 20 '16 at 12:49
|
show 2 more comments
I would bet on a transient error, however if the command tools work, and you have this error something is amiss. Maybe a BIND bug, maybe some firewall configuration (inspectors)
Your OS and BIND are quite old and EOL (2013 since it is the testing branch).
I would upgrade both urgently; if you have not kernels and BIND compiled by hand, they have already a couple nasty bugs that can be explored remotely.
If the issue continues to be present, then I would debug further on the problem.
answered Jun 17 '16 at 10:49
Rui F RibeiroRui F Ribeiro
40.1k1479136
1
Thank you. I will upgrade distribution and bind ant let you know
– gedO
Jun 17 '16 at 10:51
This weekend I have upgraded system from Debian 6 to Debian 7. Bind installed version 1:9.8.4.dfsg.P1-6+nm, but still getting same error.
– gedO
Jun 20 '16 at 12:14
Interesting. While we did not deleted the hints about your servers, it seemed to me I could connect to your powerdns server, but not your BIND server from the outside. A chance is also increasing the debug level of BIND, or increasing monitoring in some other way. Do you have firewalls in the way to outside, PIXes or ASAs? Why not Debian 8? I am running it here.
– Rui F Ribeiro
Jun 20 '16 at 12:41
Yes, I have two DNS servers, one BIND ant second PowerDNS. ip route get shows that to that IP address I go over public IP address, so no firewall is in the way
– gedO
Jun 20 '16 at 12:47
Having a route of public IP addresses is no guarantee there are no firewalls, however I do trust you know better about your setup. I am a little busy right now, will came back later with ideas for debugging.
– Rui F Ribeiro
Jun 20 '16 at 12:49
|
show 2 more comments
I would bet on a transient error, however if the command tools work, and you have this error something is amiss. Maybe a BIND bug, maybe some firewall configuration (inspectors)
Your OS and BIND are quite old and EOL (2013 since it is the testing branch).
I would upgrade both urgently; if you have not kernels and BIND compiled by hand, they have already a couple nasty bugs that can be explored remotely.
If the issue continues to be present, then I would debug further on the problem.
answered Jun 17 '16 at 10:49
Rui F RibeiroRui F Ribeiro
40.1k1479136
I would bet on a transient error, however if the command tools work, and you have this error something is amiss. Maybe a BIND bug, maybe some firewall configuration (inspectors)
Your OS and BIND are quite old and EOL (2013 since it is the testing branch).
I would upgrade both urgently; if you have not kernels and BIND compiled by hand, they have already a couple nasty bugs that can be explored remotely.
If the issue continues to be present, then I would debug further on the problem.
answered Jun 17 '16 at 10:49
Rui F RibeiroRui F Ribeiro
40.1k1479136
edited Feb 3 '18 at 1:28
answered Jun 17 '16 at 10:49
Rui F RibeiroRui F Ribeiro
40.1k1479136
answered Jun 17 '16 at 10:49
Rui F RibeiroRui F Ribeiro
40.1k1479136
answered Jun 17 '16 at 10:49
Rui F RibeiroRui F Ribeiro
40.1k1479136
40.1k1479136
1
Thank you. I will upgrade distribution and bind ant let you know
– gedO
Jun 17 '16 at 10:51
This weekend I have upgraded system from Debian 6 to Debian 7. Bind installed version 1:9.8.4.dfsg.P1-6+nm, but still getting same error.
– gedO
Jun 20 '16 at 12:14
Interesting. While we did not deleted the hints about your servers, it seemed to me I could connect to your powerdns server, but not your BIND server from the outside. A chance is also increasing the debug level of BIND, or increasing monitoring in some other way. Do you have firewalls in the way to outside, PIXes or ASAs? Why not Debian 8? I am running it here.
– Rui F Ribeiro
Jun 20 '16 at 12:41
Yes, I have two DNS servers, one BIND ant second PowerDNS. ip route get shows that to that IP address I go over public IP address, so no firewall is in the way
– gedO
Jun 20 '16 at 12:47
Having a route of public IP addresses is no guarantee there are no firewalls, however I do trust you know better about your setup. I am a little busy right now, will came back later with ideas for debugging.
– Rui F Ribeiro
Jun 20 '16 at 12:49
|
show 2 more comments
1
Thank you. I will upgrade distribution and bind ant let you know
– gedO
Jun 17 '16 at 10:51
This weekend I have upgraded system from Debian 6 to Debian 7. Bind installed version 1:9.8.4.dfsg.P1-6+nm, but still getting same error.
– gedO
Jun 20 '16 at 12:14
Interesting. While we did not deleted the hints about your servers, it seemed to me I could connect to your powerdns server, but not your BIND server from the outside. A chance is also increasing the debug level of BIND, or increasing monitoring in some other way. Do you have firewalls in the way to outside, PIXes or ASAs? Why not Debian 8? I am running it here.
– Rui F Ribeiro
Jun 20 '16 at 12:41
Yes, I have two DNS servers, one BIND ant second PowerDNS. ip route get shows that to that IP address I go over public IP address, so no firewall is in the way
– gedO
Jun 20 '16 at 12:47
Having a route of public IP addresses is no guarantee there are no firewalls, however I do trust you know better about your setup. I am a little busy right now, will came back later with ideas for debugging.
– Rui F Ribeiro
Jun 20 '16 at 12:49
1
1
Thank you. I will upgrade distribution and bind ant let you know
– gedO
Jun 17 '16 at 10:51
Thank you. I will upgrade distribution and bind ant let you know
– gedO
Jun 17 '16 at 10:51
This weekend I have upgraded system from Debian 6 to Debian 7. Bind installed version 1:9.8.4.dfsg.P1-6+nm, but still getting same error.
– gedO
Jun 20 '16 at 12:14
This weekend I have upgraded system from Debian 6 to Debian 7. Bind installed version 1:9.8.4.dfsg.P1-6+nm, but still getting same error.
– gedO
Jun 20 '16 at 12:14
Interesting. While we did not deleted the hints about your servers, it seemed to me I could connect to your powerdns server, but not your BIND server from the outside. A chance is also increasing the debug level of BIND, or increasing monitoring in some other way. Do you have firewalls in the way to outside, PIXes or ASAs? Why not Debian 8? I am running it here.
– Rui F Ribeiro
Jun 20 '16 at 12:41
Interesting. While we did not deleted the hints about your servers, it seemed to me I could connect to your powerdns server, but not your BIND server from the outside. A chance is also increasing the debug level of BIND, or increasing monitoring in some other way. Do you have firewalls in the way to outside, PIXes or ASAs? Why not Debian 8? I am running it here.
– Rui F Ribeiro
Jun 20 '16 at 12:41
Yes, I have two DNS servers, one BIND ant second PowerDNS. ip route get shows that to that IP address I go over public IP address, so no firewall is in the way
– gedO
Jun 20 '16 at 12:47
Yes, I have two DNS servers, one BIND ant second PowerDNS. ip route get shows that to that IP address I go over public IP address, so no firewall is in the way
– gedO
Jun 20 '16 at 12:47
Having a route of public IP addresses is no guarantee there are no firewalls, however I do trust you know better about your setup. I am a little busy right now, will came back later with ideas for debugging.
– Rui F Ribeiro
Jun 20 '16 at 12:49
Having a route of public IP addresses is no guarantee there are no firewalls, however I do trust you know better about your setup. I am a little busy right now, will came back later with ideas for debugging.
– Rui F Ribeiro
Jun 20 '16 at 12:49
|
show 2 more comments
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f290363%2fbind9-socket-c-unexpected-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hi welcome to slashdot. Add Linux version/software versions to this post and any future posts please. It seems BIND was unable to connect to that IP. Could be a transient error. Is it your BIND configured for IPv6 only or is the IPv4 interface down? Have you allowed besides UDP/53, TCP/53, if using firewall rules? Test 198.41.0.4 with a dig/nslookup from the BIND machine
– Rui F Ribeiro
Jun 17 '16 at 10:30
Have you restarted named?
– Rui F Ribeiro
Jun 17 '16 at 10:46
Several times, same problem
– gedO
Jun 17 '16 at 10:47
what does
sudo tcpdump -nvvv host 198.41.0.4says? leave it running until you have a couple of answers.– Rui F Ribeiro
Jun 20 '16 at 13:12
Tcpdump captures: pastebin.com/77cLNBk4
– gedO
Jun 20 '16 at 13:27