History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JM-1203
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Daniel Henninger
Reporter: Scott Hirdes
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Openfire

Open fire doesn't do a DNS lookup on sub domains for server-to-server communications

Created: 12/06/07 04:41 PM   Updated: 04/22/08 09:33 PM
Component/s: None
Affects Version/s: 3.4.1
Fix Version/s: 3.5.1

Time Tracking:
Not Specified

File Attachments: 1. Text File subdomain_communication.patch (0.8 kb)


Support Plan Customer Issue: No
Resolution Date: 04/22/08 09:33 PM
Acceptance Test - Add?: No


 Description  « Hide
If you are trying to send a message to a JID where the DNS name is a subdomain of the XMPP server domain, Openfire does not do a DNS lookup and instead assumes that the address specified is a local service. Therefore, the message is never sent to the other server but instead the server attempts to route the message to an internal service that doesn't exist.

If the address is not a registered component of Openfire, Openfire should do a DNS lookup and attempt server to server communication.



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Scott Hirdes - 12/18/07 05:57 PM
This is actually not just a subdomain issue. If the server name string of the remote server being sent to contains the string of the local server, packets will not be sent via server to server.

For example, if a server with the name chat.domain.com is trying to send to the address mychat.domain.com, a DNS lookup is not done on "mychat.domain.com" because that string contains "chat.domain.com"