Unable to send message between two xmpp servers

hi-

i have two xmpp servers set up - one running openfire 3.8.1, and another running ejabberd 2.1.10. the openfire server is my primary server, serving jid@example.com. i’ve recently set up the ejabberd server for the purposes of doing some testing, and have configured it to serve jid@vc.example.com.

the openfire server has been in use for quite some time, and has worked as expected, both in terms of c2s and s2s/federated communication, etc. on both servers, i’m able to successfully send messages between directly connected users. however, i’m having some trouble with s2s, between the two servers. i’m able to send a message from an ejabberd user to an openfire user, but i’m not able to send a message from an openfire user to an ejabberd user.

i’ve enabled debug logging on the openfire server, and see this in debug.log:

2013.04.09 08:51:29 org.jivesoftware.openfire.spi.RoutingTableImpl - RoutingTableImpl: Failed to route packet to JID: jdoe@vc.example.net packet: test

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: Trying to find a user’s DN based on their username. uid: jdoe, Base DN: dc=“example”,dc=“net”…

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: Creating a DirContext in LdapManager.getContext()…

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: connection pooling was requested but has been disabled because of StartTLS.

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: Created hashtable with context values, attempting to create context…

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: … StartTlsRequest

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: … peer host: dsa1.example.net, CipherSuite: TLS_RSA_WITH_AES_256_CBC_SHA

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: … context created successfully, returning.

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: Starting LDAP search…

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: … search finished

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: User DN based on username ‘jdoe’ not found.

2013.04.09 08:51:29 org.jivesoftware.openfire.ldap.LdapManager - LdapManager: Exception thrown when searching for userDN based on username ‘jdoe’

org.jivesoftware.openfire.user.UserNotFoundException: Username jdoe not found

how can i get it to tell my why it fails to route packet to jdoe@vc.example.net, and why is it looking in ldap for this? i believe i have the requisite dns records in place, srv and otherwise:

_jabber._tcp.vc.example.net. 86400 IN SRV 10 0 5269 vc-mgr.example.net.

_xmpp-client._tcp.vc.example.net. 86400 IN SRV 10 0 5222 vc-mgr.example.net.

_xmpp-server._tcp.broadcast.vc.example.net. 86400 IN SRV 10 0 5269 vc-mgr.example.net.

_xmpp-server._tcp.conference.vc.example.net. 86400 IN SRV 10 0 5269 vc-mgr.example.net.

_xmpp-server._tcp.pubsub.vc.example.net. 86400 IN SRV 10 0 5269 vc-mgr.example.net.

_xmpp-server._tcp.search.vc.example.net. 86400 IN SRV 10 0 5269 vc-mgr.example.net.

_xmpp-server._tcp.vc.example.net. 86400 IN SRV 10 0 5269 vc-mgr.example.net.

vc.example.net. 300 IN A 192.168.1.80

vc-mgr.example.net. 300 IN A 192.168.1.80

thanks

-ben

it seems as though it’s perhaps an issue of the ejabberd server being a subdomain of the openfire server? there are a number of similar discussions i’ve come across, over the years:

and a bug fix that is referenced from the first discussion above:

http://issues.igniterealtime.org/browse/JM-1203

it’s allegedly been fixed, but has there perhaps been a regression? this seems to quite specifically echo the experience i’m having, as well as the other discussions above, two of which are from after 2011.

is there a more formal method for asking that this be looked into again, aside from hoping someone will read this particular discussion?

-ben