Open fire doesn't do a DNS lookup on sub domains for server-to-server communications
Description
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.
Environment
None
Attachments
1
Activity
Show:
Tsyopa Dmitry April 26, 2012 at 9:23 AM
I failed to download this patch - the link to patch file is broken (server responds "Could not find the specified attachment on the server"), could anybody fix it, please.
Scott Hirdes December 19, 2007 at 7:57 AM
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"
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.