Openfire (ARCHIVED)

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

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.4.1
  • Fix Version/s: 3.5.1
  • Component/s: None
  • Labels:
    None
  • Acceptance Test - Add?:
    No

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.

Activity

Hide
Scott Hirdes added a comment -

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"

Show
Scott Hirdes added a comment - 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"

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: