https://www.ejabberd.im/node/632 en https://www.ejabberd.im/node/632#comment-1335 <div class="quote-msg"> <div class="quote-author"><em>sander</em> wrote:</div> <p>After you did that you can ask someone not in your LAN to ping "randomsubdomain.cradle.dyndns.org" if he gets your IP, it should work! :-)</p></div> <p>And work it did!</p> <p>I've enabled wild cards, and it now does resolve correctly from non-lan computers. Thank you heaps for the help, I have no idea how long it would have taken me to realise that oversight!</p> <p>I had to restart pretty much everything, or maybe I just had to wait for the dns changes to roll out, either way it's working now.</p> <p>Thanks for the help Sander :) It's a bit slow, but it seems to be working now, thanks a bunch!</p> <p>A happy ejabberd user,</p> <p> - Glenn</p> Thu, 02 Feb 2006 08:37:46 +0000 cradle@jabber.org.au comment 1335 at https://www.ejabberd.im https://www.ejabberd.im/node/632#comment-1333 <div class="quote-msg"> <div class="quote-author"><em>cradle@jabber.org.au</em> wrote:</div> <p>I have configured a local ejabberd server on an Ubuntu box, and all seems to be going swell. s2s works for chatting and such, but s2s service discovery to my box from another server seems to not work as well as I'd hope.</p> <p>This screenshot pretty much explains my situation...</p> <p><noindex><a href="http://www.users.on.net/~murraymob/discovery.PNG" rel="nofollow" >http://www.users.on.net/~murraymob/discovery.PNG</a></noindex></p></div> <p>I see you use Dyndns like me. You need to make sure that all the sub domains are resolvable from the Internet. You can do this by enabling an option in your Dyndns.org account to make all sub domains resolvable. It is called wildcard AFAIR. After you did that you can ask someone not in your LAN to ping "randomsubdomain.cradle.dyndns.org" if he gets your IP, it should work! :-)</p> Thu, 02 Feb 2006 08:26:00 +0000 sander comment 1333 at https://www.ejabberd.im