[Pidgin] #9984: Google STUN lookup fails when using SOCKS 5 proxy

[Pidgin]

#9984: Google STUN lookup fails when using SOCKS 5 proxy
---------------------+------------------------------------------------------
 Reporter:  spidey3  |        Owner:  deryni
     Type:  defect   |       Status:  new   
Milestone:           |    Component:  XMPP  
  Version:  2.6.1    |   Resolution:        
 Keywords:           |  
---------------------+------------------------------------------------------
Description changed by spidey3:

Old description:

> I am running 2.6.1 on Windows XP and have a globally configured SOCKS 5
> proxy [in Tools -> Preferences -> Network], with Google XMPP account
> configured with Use Global Proxy Settings.
>
> I notice, however, the following in my debug window:
>
> (09:38:07) dnsquery: Performing DNS lookup for stun.l.google.com
> (09:38:07) dnsquery: Error resolving stun.l.google.com: 11004
> (09:38:07) jabber: Google STUN lookup failed: Error resolving
> stun.l.google.com: 11004
>
> It would appear that the DNS lookup for the stun server is being done
> using the local DNS -- even though with SOCKS 5 it should be done through
> the proxy.

New description:

 I am running 2.6.1 on Windows XP and have a globally configured SOCKS 5
 proxy [in Tools -> Preferences -> Network], with Google XMPP account
 configured with Use Global Proxy Settings.

 I notice, however, the following in my debug window:


 {{{
 (09:38:07) dnsquery: Performing DNS lookup for stun.l.google.com
 (09:38:07) dnsquery: Error resolving stun.l.google.com: 11004
 (09:38:07) jabber: Google STUN lookup failed: Error resolving
 stun.l.google.com: 11004
 }}}


 It would appear that the DNS lookup for the stun server is being done
 using the local DNS -- even though with SOCKS 5 it should be done through
 the proxy.

--

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9984#comment:1>
Pidgin <http://pidgin.im>
Pidgin