Comment 26 for bug 578265

Revision history for this message
In , Will Thompson (wjt) wrote :

(In reply to comment #17)
> Reducing severity: this works in at least some networks (we can't reproduce it
> here). If this bug affects you, please provide the information I requested in
> Comment #16 and we can try to work out what's going wrong.

I can now reproduce this on one of my internet connections, and have worked around it in Wocky. The problem is that _xmpp-client._tcp.chat.facebook.com is a CNAME for chat.facebook.com, rather than an SRV record.

See http://git.collabora.co.uk/?p=user/wjt/wocky.git;a=commitdiff;h=refs/heads/work-around-chat.facebook.com for the patch!

 % host -t SRV _xmpp-client._tcp.chat.facebook.com
_xmpp-client._tcp.chat.facebook.com is an alias for chat.facebook.com.
 % host -v -t SRV _xmpp-client._tcp.chat.facebook.com
Trying "_xmpp-client._tcp.chat.facebook.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19955
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;_xmpp-client._tcp.chat.facebook.com. IN SRV

;; ANSWER SECTION:
_xmpp-client._tcp.chat.facebook.com. 7 IN CNAME chat.facebook.com.

;; AUTHORITY SECTION:
facebook.com. 37 IN SOA glb01.sf2p.tfbnw.net. hostmaster.facebook.com. 2157 10800 3600 604800 60

Received 134 bytes from 192.168.99.1#53 in 43 ms