Article delegate-en/3723 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
[Reference:<_A3722@delegate-en.ML_>]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: Unknown UDP ports
24 Apr 2007 11:53:48 GMT Peter Rabbitson <prehabdyi-5vjbuj7frptr.ml@ml.delegate.org>


Yutaka Sato wrote:
> In message <_A3721@delegate-en.ML_> on 04/23/07(18:39:20)
> you Peter Rabbitson <prehabdyi-5vjbuj7frptr.ml@ml.delegate.org> wrote:
>  |I am successfully running delegate, no problems no issues (I am also
>  |aware that there is a new version, have not upgraded yet). However
>  |besides binding on the 8080 pot as requested, delegate binds on two more
>  |unprivileged udp ports. Can someone explain what is delegate doing? Here
>  |is my config:
> ...
>  |Arx:/usr/local/delegate# netstat -an46p | grep delegate
>  |tcp        0   0 0.0.0.0:8080  0.0.0.0:* LISTEN   11280/delegated -{0
>  |udp        0   0 0.0.0.0:4588  0.0.0.0:*          11280/delegated -{0
>  |udp      324   0 0.0.0.0:4589  0.0.0.0:*          11280/delegated -{0
> 
> The UDP ports are for the DNS resolver of DeleGate.
> 
> <snip>
> 
> You can suppress the ports if you rely on the default resolvers of the
> host machine, with the parameter as this:
> 
>   RESOLV=sys
> 

Yes, this works. Just of curiosity, why the default order of RESOLV
gives higher priority to 'dns' as opposed to 'sys'? Is there a certain
rationale behind doing own dns queries instead of asking the system
which most of the time even has some sort of local caching in the first
place?

Thanks for the great software!

Peter

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
@_@V