Operating System - HP-UX
1835624 Members
2955 Online
110080 Solutions
New Discussion

Re: Named: not listening on any interfaces

 
Cary Farah
Frequent Advisor

Re: Named: not listening on any interfaces


I have found the reason that /usr/sbin/named was not listening on any port;
however, I'm not sure of the repercussions of the fix.

The normal startup of named begins with:

starting BIND 9.2.0
using X CPUS
loading configuration from '/etc/named.conf'
no IPv6 interfaces found
listening on IPv4 interface lanX, xxx.xxx.xxx.xxx#53
listening on IPv4 interface lo0, 127.0.0.1#53

I downloaded a couple of tools onto your machine in
/usr/contrib/bin

lsof - list open files
tusc - trace unix system calls

What I thought initially was that there was something
interfering with opening a UDP port 53; however, this
proved not to be the case. Checked with lsof.

At that point I started /usr/sbin/named while tracing
the execution with tusc. I also traced my system to
see where the two deviated. That occured here:

From your system:

{89853} <-0.000000> stat("/dev/ip6", 0x7f7f0670) ......... [entry]
{89853} <0.000402> stat("/dev/ip6", 0x7f7f0670) .......... = 0
{89853} <-0.000000> getsockname(0, 0x7f7f06d8, 0x7f7f0870) [entry]
{89853} <0.000126> getsockname(0, 0x7f7f06d8, 0x7f7f0870) ERR#216 ENOTSOCK
{89853} <-0.000000> open("/dev/log", O_WRONLY|O_NONBLOCK, 05050) [entry]
{89853} <0.000346> open("/dev/log", O_WRONLY|O_NONBLOCK, 05050) = 4

From my system:

{34177} <-0.000000> sigsetreturn(0x7b01efce, 0x6211988, 1392) [entry]
{34177} <0.000038> sigsetreturn(0x7b01efce, 0x6211988, 1392) ..... = 0
{34177} <-0.000000> stat("/dev/ip6", 0x7f7e10d0) ............. [entry]
{34177} <0.000162> stat("/dev/ip6", 0x7f7e10d0) ......... ERR#2 ENOENT
{34177} <-0.000000> open("/dev/log", O_WRONLY|O_NONBLOCK, 0) . [entry]
{34177} <0.000132> open("/dev/log", O_WRONLY|O_NONBLOCK, 0) ...... = 4
{34177} <-0.000000> fcntl(4, F_SETFD, 1) ..................... [entry]
{34177} <0.000043> fcntl(4, F_SETFD, 1) .......................... = 0

What I noticed different here was that when /dev/ip6 was found on your
system "named" that the call to getsockname() failed. On my system,
I had no /dev/ip6 so I kept going there instead of failing. I renamed
/dev/ip6 on your system to /dev/ip6.save. When I did this, your "named"
came up listening.

I think this could be a bug in /usr/sbin/named or it could be a
configuration issue with IPv6 once named gets to that point in the logic.
That is the focus of my investigation at this time.

I will pursue this with my expert center.

Regards,

Mark Bettis
Sachin Patel
Honored Contributor

Re: Named: not listening on any interfaces

Woo who whould have thought about that.
Is photography a hobby or another way to spend $