Change Server Name

Openfire Openfire Support
1

Wildfire 2.6.2

Windows 2000 Server

Embedded database

When I setup wildfire originally, I gave it the server name of the windows computer name. Example: server1.example.com

We started using Spark 2 and now is shows the full user name, so it shows: user@server1.example.com.

I don’'t really like that and would prefer is just said user@example.com.

If I change the in the web admin console, in Server Manager / Server Settings, the server name to example.com with that affect anything? Is is ok to do?

Thanks,

David Steven

2

Hi David,

That’‘s perfectly fine. So, all users will have to enter the server name as example.com when they login. However, you’'ll have to make sure that your clients will resolve example.com to the ip address of server1.example.com.

3

Hi David,

if this is a clean installation it will be fine. For MUC and rosters this will be really bad as Wildfire stores the whole username and not a reference to it. So you may want to check the database and edit all server name values there.

LG

4

Primarily running spark on a LAN, users have been using “server1” as the server name in the Spark login box. not server1.example.com.

So in Spark, as long as whatever the client uses for server resolves to the box running wildfire it will connect?

Then what does the “server name” in wildfire mean or apply to?

5

Hi,

Spark uses the domain the server sends to it, no matter what you use to connect to Wildfire. So if you add one guy to a roster then you may have “user@server1” on your roster. This is of course not the same as "user@example.com" I wonder what will happen.

LG

6

Hi David,

Whatever the xmpp.domain that you set in Wildfire, Spark must follow as is in the server name in order to successfully connect to Wildfire. That means, not even a short form of the name. Please don’‘t get confused with the server name and the ability to connect. To Spark, it must know how to connect its user as user@ xmpp.domain. That’'s what the server name means. On the contrary, the ability to connect for Spark depends on either to resolve the xmpp.domain, or to directly use the ip address you specify in the “Preference” window (if you click on the “Advance” button). The former requires you to have a DNS or at least an entry of xmpp.domain in you /etc/hosts (if unix). The later, if enabled, will overide the former.

However, as LG mentioned, once you change the xmpp.domain you’‘ll have to change all references of xmpp.domain in Wildfire database prior to Wildfire execution, or you’'ll get unexpected behavior.

Message was edited by: aznidin