Interesting socket binding in 9.5.0a5

Adam Tkac atkac at redhat.com
Thu Jun 21 17:00:34 UTC 2007


Hi all,

I've start using bind 9.5 and first problem comes very quickly. Does 
anybody know why BIND binding sockets on random ports (I often overlook 
some feature :) )? This looks more like bug for me. This is stripped 
output from named (with -g option)

21-Jun-2007 18:49:49.549 socket 0xb7f465c8 0.0.0.0#0: bound
21-Jun-2007 18:49:49.550 socket 0xb7f46738 ::#0: bound
21-Jun-2007 18:49:49.552 socket 0xb7f468a8 0.0.0.0#5698: bound
21-Jun-2007 18:49:49.552 socket 0xb7f46a18 ::#2217: bound
21-Jun-2007 18:49:49.553 socket 0xb7f46b88 0.0.0.0#58938: bound
21-Jun-2007 18:49:49.554 socket 0xb7f46cf8 ::#32169: bound
21-Jun-2007 18:49:49.554 socket 0xb7f46e68 0.0.0.0#48835: bound
21-Jun-2007 18:49:49.555 socket 0xb7f66008 ::#40744: bound
21-Jun-2007 18:49:49.555 socket 0xb7f66178 0.0.0.0#20884: bound
21-Jun-2007 18:49:49.556 socket 0xb7f662e8 ::#47394: bound
21-Jun-2007 18:49:49.556 socket 0xb7f66458 0.0.0.0#33318: bound
21-Jun-2007 18:49:49.557 socket 0xb7f665c8 ::#18373: bound
21-Jun-2007 18:49:49.557 socket 0xb7f66738 0.0.0.0#41954: bound
21-Jun-2007 18:49:49.558 socket 0xb7f668a8 ::#20406: bound
21-Jun-2007 18:49:49.559 socket 0xb7f66a18 0.0.0.0#23665: bound
21-Jun-2007 18:49:49.559 socket 0xb7f66b88 ::#44600: bound
21-Jun-2007 18:49:49.560 socket 0xb7f66cf8 0.0.0.0#53329: bound
21-Jun-2007 18:49:49.560 socket 0xb7f66e68 ::#59432: bound

I'm using SELinux on some machines so it killing named due this.

Regards, Adam


More information about the bind-workers mailing list