BIND bound to high port?

T. Esting T_Esting at excite.com
Fri Jan 14 21:48:25 UTC 2000


   I have several different BIND-s running on various machines.  On a
couple, 
I see a random UDP high port bound that I don't typically expect to see 
(file descriptor 4 in the example below): 

# lsof -i -a -p `cat /etc/named.pid` 
COMMAND  PID USER   FD   TYPE     DEVICE SIZE/OFF NODE NAME 
named   6780 root    4u  inet 0x61167750      0t0  UDP *:44033 (Idle) 
named   6780 root   20u  inet 0x6743dcd0      0t0  UDP localhost:domain
(Idle) 
named   6780 root   21u  inet 0x669e0280      0t0  TCP localhost:domain
(LISTEN) 
named   6780 root   22u  inet 0x62603ab8      0t0  UDP myhost2:domain (Idle)

named   6780 root   23u  inet 0x65613540      0t0  TCP myhost2:domain
(LISTEN) 

Can anyone shed any light regarding what it is that causes BIND to use 
this port?  My best guess is that it's somehow related to query-source 
address, but I'm dubious enough that I was hoping someone on the list might 
know for sure. 

Thanks. 





_______________________________________________________
Get 100% FREE Internet Access powered by Excite
Visit http://freeworld.excite.com




More information about the bind-users mailing list