Huge amount of connection retries and logs for non-existent realms

[nexus]

When user has contact on non-existent realm in his roster, s2s is trying to connect to server really really fast disrespecting any retry limits in configuration file.

s2s produces lots of this error messages (read something about 5 times per second these 4 lines)

Wed Jul  2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] outgoing
connection for 'jabber.example.net'
Wed Jul  2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] sending
dialback auth request for route 'smoula.net/jabber.example.net'
Wed Jul  2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] error:
Stream error (<stream:error xmlns:stream='http://etherx.jabber.org
/streams'><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error>)
Wed Jul  2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] disconnect,
packets: 2

At this concrete example I have jabber server smoula.net, my friend had jabber server on jabber.example.net. After some time he decided to move just to example.net. Unfortunately some of my users have invalid records in their rosters directing to jabber.example.net.

This happens (I think):

• s2s resolves jabber.example.net which leads to IP ie. 1.1.1.1 (which is same to just example.net)
• s2s connects to 1.1.1.1 and tries to deliver a message, presence or whatever into realm jabber.example.net)
• server on 1.1.1.1 refuses to handle this message
• s2s drops a connection and without any pause, retry limit count tries that again.