powered by Jive Software

Xmpp domain name and server/hostname do they need to be the same?

Hi Any Help Would be Appreciated,

We are trying to connect/federate Openfire Version 3.8.2 to external xmpp server.

Problem seems to be on our side, as external server federates with others and we do not.

Does our servername and xmpp domain name need to be the same?

Our external xmpp dns record is

_xmpp-server._tcp.gpi.com SRV service location:

priority = 0

weight = 0

port = 5269

svr hostname = im.gpi.com

Which resolves to IP address, but this IP address is Openfire servername: GPI-OPENFIRE1

im.gpi.com is just a CNAME used for client config.

No, they don’t.

In fact, in a cluster all machines have the same domain, but are on different servers.

I found these descriptions with regards to another app federating with Openfire and the name requirement:

Ensure that the XMPP domain (property xmpp.domain) is a FQDN that can be resolved via DNS on the Internet. This also needs to be the hostname of the machine running Openfire.

http://mytestbed.net/projects/omf54/wiki/Openfire_s2s

http://sourceforge.net/apps/mediawiki/role-project/index.php?title=ROLE_XMPP_Ser ver#How_to_prepare_an_Openfire_XMPP_server_for_federation

With this what I believe we need is that the dns srv needs to resolve to the hostname of the Openfire server.

John Cowher написал(а):

Ensure that the XMPP domain (property xmpp.domain) is a FQDN that can be resolved via DNS on the Internet. This also needs to be the hostname of the machine running Openfire.

With this what I believe we need is that the dns srv needs to resolve to the hostname of the Openfire server.

Sorry for necroposting, but can this be avoided somehow? We have two openfires here, and both servers have convenient names. Now i need an S2S, and it always ends with bunches of “Closing session due to incorrect hostname in stream header”. I guess that’s because hostnames differ from server names?

Renaming hosts is not an option here.