[jadmin] SUMMARY: Local DNS Changes Whack 1.4.3 Server

[Tim Evans]

Earlier, I wrote:

>We're running jabberd 1.4.3 on an internal network for internal messaging. 
>Recently the DNS folks inserted a new sub-domain level (i.e., going from
>"foo.bar.com" to "foo.bat.bar.com".
>
>Users now can't connect to the server, even though its numerical IP address
>has not changed.
>
>I've tried editing the jabber.xml and muc.xml files to reflect the new domain
>naming, and have tried copying the spool subdirectories to new names
>reflecting the domain naming.

This is resolved, though I'm not quite sure it worked the way it should have.

I had forgotten to change the Solaris startup script for the jabberd server to 
specify the new sub-domain.  Even after making this change and restarting 
jabberd, users were still not able to log in.

As noted, I had hand-edited the jabber.xml and muc.xml to change all usernames 
to incorporate the new subdomain and renamed the domain's subdirectory in the 
spool directory.  Still, users couldn't log in.

I had them all re-register, and all's now well, though some, but not all 
(strangely), had to use new login names.
--
Tim Evans, TKEvans.com, Inc.	|    5 Chestnut Court
tkevans at tkevans.com		|    Owings Mills, MD 21117
http://www.tkevans.com/		|    443-394-3864
http://www.come-here.com/News/	|