Hi there, I sincerely hope I directed my issue to the correct mailing list. I think I stumbled upon some odd behaviour in prosody's DNS resolution, but I am not sure if I interpreted the logs correctly.
Here is the short version of what I think happens: 1) Attempt to connect to another server via s2s 2) No SRV record found, A/AAAA is tried. 3) AAAA DNS reply arrives first. As the domain name is a CNAME, but has no IPv6 address, the reply contains just the CNAME. 4) A DNS reply arrives after the AAAA reply. The answer contains the CNAME and an A record. 5) Nonetheless, prosody logs "DNS lookup failed". Please see attached debug.log and DNS pcap. I shortened them to contain only the relevant connection. The DNS error is also shown in my client (Gajim). During my pcap-capture, after the first failed connection attempt two other connection attempts were made (to the same server), both successful. Both times, the response with the a record arrived before the one with the AAAA record. I think I can rule out some general DNS issue, as connections to all other servers in my contact list work flawlessly. I think the problematic one is the only one with this specific DNS configuration (CNAME + no AAAA record). My prosody version is 0.9.7 on a FreeBSD 10.1 virtual machine. The DNS server is unbound, located on the host of the VM (FreeBSD 10.1). Please do not hesitate to ask if you need additional information. I will also gladly file a bug if you guys have ruled out errors in my interpretation of the logs. Thank you very much :-) Michael -- Michael Pfeiffer <michael.pfeif...@eichenstein.de> -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at http://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
Apr 13 14:18:15 trinity prosody[59512]: mod_s2s: First attempt to connect to eris.prakinf.tu-ilmenau.de, starting with SRV lookup... Apr 13 14:18:15 trinity prosody[59512]: adns: Records for _xmpp-server._tcp.eris.prakinf.tu-ilmenau.de. not in cache, sending query (thread: 0x804d88d40)... Apr 13 14:18:15 trinity prosody[59512]: adns: Sending DNS query to 192.168.1.1 Apr 13 14:18:15 trinity prosody[59512]: stanzarouter: Routing to remote... Apr 13 14:18:15 trinity prosody[59512]: adns: Reply for _xmpp-server._tcp.eris.prakinf.tu-ilmenau.de. (thread: 0x804d88d40) Apr 13 14:18:15 trinity prosody[59512]: mod_s2s: eris.prakinf.tu-ilmenau.de has no SRV records, falling back to A/AAAA Apr 13 14:18:15 trinity prosody[59512]: adns: Records for eris.prakinf.tu-ilmenau.de not in cache, sending query (thread: 0x805078900)... Apr 13 14:18:15 trinity prosody[59512]: adns: Sending DNS query to 192.168.1.1 Apr 13 14:18:15 trinity prosody[59512]: adns: Records for eris.prakinf.tu-ilmenau.de not in cache, sending query (thread: 0x805078a80)... Apr 13 14:18:15 trinity prosody[59512]: adns: Sending DNS query to 192.168.1.1 Apr 13 14:18:15 trinity prosody[59512]: adns: Reply for eris.prakinf.tu-ilmenau.de (thread: 0x805078a80) Apr 13 14:18:15 trinity prosody[59512]: adns: Reply for eris.prakinf.tu-ilmenau.de (thread: 0x805078900) Apr 13 14:18:15 trinity prosody[59512]: mod_s2s: DNS lookup failed to get a response for eris.prakinf.tu-ilmenau.de Apr 13 14:18:15 trinity prosody[59512]: mod_s2s: No other records to try for eris.prakinf.tu-ilmenau.de - destroying Apr 13 14:18:15 trinity prosody[59512]: s2sout8051f4740: Destroying outgoing session matrixnode.net->eris.prakinf.tu-ilmenau.de: DNS resolution failed
dns-shortend.pcap
Description: application/vnd.tcpdump.pcap
