bind listening on strange port
I upgraded a couple of weeks ago to bind-8.1.2-1, and
recently noticed that it's listening on a port slightly
above 1024; on one system it's 1026, another 1028.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF INODE NAME
named 92 root 4u inet 0x008d3c0c 0t0 UDP *:1026
Connecting to this port via netcat produces the
following in syslog:
May 15 15:39:30 ithilien named: refused query on
non-query socket from [127.0.0.1].1033
My question is, when did bind start listening on
this port, and why?
Jacob Langseth <email@example.com>
CTI Engineer -- Enhanced Systems, Inc.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com