[Serusers] Mediaproxy / proxydispatcher: couldn't retrieve DNS SRV record

[Greger V. Teigre]

I would look at the error: Connection refused
and start looking for the reason (firewall? error in /etc/resolv.conf?)
g-)

kjcsb wrote:
> I am getting the following error in the log file:
>
>
>
> Sep 28 06:24:25 beta proxydispatcher[24129]: error: couldn't retrieve 
> DNS SRV record '_mediaproxy._tcp.domain.co.nz': (111, 'Connection 
> refused')
>
>
>
> However I think the DNS records are OK.
>
>
>
> dig SRV _mediaproxy._tcp.domain.co.nz
>
>
>
> ; <<>> DiG 9.2.3 <<>> SRV _mediaproxy._tcp.domain.co.nz
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63894
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 2, ADDITIONAL: 3
>
>
>
> ;; QUESTION SECTION:
> ;_mediaproxy._tcp.domain.co.nz. IN  SRV
>
>
>
> ;; ANSWER SECTION:
> _mediaproxy._tcp.domain.co.nz. 86100 IN SRV 0 100 25060 
> c-mp-03.domain.co.nz.
> _mediaproxy._tcp.domain.co.nz. 86100 IN SRV 10 50 25060 
> c-mp-01.domain.co.nz.
> _mediaproxy._tcp.domain.co.nz. 86100 IN SRV 10 50 25060 
> c-mp-02.domain.co.nz.
>
>
>
> ;; AUTHORITY SECTION:
> domain.co.nz.       258929  IN      NS      ns2.widge.net.
> domain.co.nz.       258929  IN      NS      ns1.widge.net.
>
>
>
> ;; ADDITIONAL SECTION:
> c-mp-03.domain.co.nz. 86129 IN      A       60.234.nnn.nnn
> ns1.widge.net.          170576  IN      A       82.165.160.211
> ns2.widge.net.          170576  IN      A       82.165.163.115
>
>
>
> ;; Query time: 83 msec
> ;; SERVER: 64.62.196.100#53(64.62.196.100)
> ;; WHEN: Thu Sep 28 06:28:07 2006
> ;; MSG SIZE  rcvd: 276
>
>
>
> On the target server (c-mp-03.domain.co.nz) there's something getting 
> through to to mediaproxy as shown in the log file:
>
>
>
> Sep 28 06:26:21 domain01 mediaproxy[16128]: command status
> Sep 28 06:26:21 domain01 mediaproxy[16128]: command execution time:  
> 0.54 ms
> Sep 28 06:26:41 domain01 mediaproxy[16128]: command status
> Sep 28 06:26:41 domain01 mediaproxy[16128]: command execution time:  
> 0.55 ms
>
>
>
> Could anyone advise how to resolve this issue?
>
>
>
> Regards
>
>
>
> Cameron
>
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
>