Pidgin dns query issues (xmpp)

[Lantern]

Ethan Blanton-3 wrote:
> 
> Lantern spake unto us the following wisdom:
>> I've been having an issue with dns resolution in pidgin. I've got an
>> isolated
>> LAN with three RHEL5 boxes. They have the following ip addresses and
>> functions:
>> 
>> 10.52.0.34: dns server (BIND9), mysql database, pidgin client
>> 10.52.0.35: pidgin client, openfire jabber server
>> 10.52.0.36: pidgin client
>> 
>> On 34, I've set "example.com" to resolve to 10.52.0.34, and I've set the
>> dns
>> server on all three boxes to be 34 as well. Pinging "example.com" returns
>> 34
>> on each box, and a small c program I've written resolves example.com to
>> be
>> 34 via the getaddrinfo function. However, I am having the following issue
>> with pidgin:
> 
>>Is your description here correct?  You claim that .34 is example.com,
>>but that the openfire server is running on .35, and that XMPP
>>connections to example.com correctly locate the openfire server.  Are
>>you using SRV records?
> 
> I'm not using SRV records right now; I'm simply using A records.
> example.com does
> indeed resolve to .34. The openfire server runs on .35, which remotely
> connects to
> the database on .34 (yeah, I know, really efficient :P). I'm trying to
> figure out whether
> my issue lies within pidgin or openfire.
> 
> 
>> When I register a user with the domain "example.com," the process is
>> successful, and when I view active sessions in openfire, the user shows
>> up
>> on the list. However, when I register 2 users on 2 different machines,
>> and
>> then I try to send chat messages between them via the "example.com"
>> domain,
>> the messages are not received either way. Furthermore, when I try to add
>> the
>> other as a buddy via the "example.com" domain, the authorization process
>> is
>> never shown to take place on the other end.
>> 
>> Both message sending and buddy-adding is successful when I specify the
>> actual ip address 10.52.0.34 as the domain.
>> 
>> I've been looking through \pidgin-2.1.0\libpurple\dnsquery.{c, h} in
>> order
>> to see how the dns query works, but nothing stands out to me as code that
>> would prevent proper dns resolution only for sending messages. Is anyone
>> familiar with this problem, and can anyone advise me on my issue?
> 
>>The debug output from Pidgin might be illuminating (via the debug
>>window, or the output of pidgin -d), as might a packet dump
>>(particularly if you are not using SSL, or if you can turn SSL off for
>>testing).
> 
> Ethan
> 
> -- 
> The laws that forbid the carrying of arms are laws [that have no remedy
> for evils].  They disarm only those who are neither inclined nor
> determined to commit crimes.
> 		-- Cesare Beccaria, "On Crimes and Punishments", 1764
> 
>  
> _______________________________________________
> Devel mailing list
> Devel at pidgin.im
> http://pidgin.im/cgi-bin/mailman/listinfo/devel
> 
> 

-- 
View this message in context: http://www.nabble.com/Pidgin-dns-query-issues-%28xmpp%29-tf4628839.html#a13219475
Sent from the Pidgin - Development mailing list archive at Nabble.com.