| Author |
Message |
|
| Guest |
 Posted: Sun Jul 09, 2006 1:02 am |
 |
|
|
Guest
|
*turns off the klaxon alarms* Hey, I can't uh... afford a DNS service that provides SRV records. Can't figure out how to do them on my own either. So I assume that's the reason why everyone with an account at jabber.org, jabber.com, and any other remote server, does not receieve presence notification from accounts on my server?
I'm running a little server using ejabberd updated last on June 1st. It's really frustrating and I don't know how to deal with it. I want to be compatible with other servers as much as possible, but just can't make heads nor tails of this presence thing. As well, intermittently messages will just fail to be delivered returning unexplained 404 errors and 500 errors, the only explanation being "Message failed to be delivered."
Another odd thing is I receive presence just fine. When someone signs onto jabber.org, my users see them sign on. It just doesn't happen vice versa, and many times there's that delivery failure that should never happen. Any ideas?
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived frommailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jul 09, 2006 8:22 am |
|
|
|
Guest
|
Hello,
you have to tell Erlang to use the native dns resolver. Look for erl, ejabberd and inetrc on the web.
--
Micka |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jul 09, 2006 8:49 am |
|
|
|
Guest
|
On 09 Jul 2006 10:22:00 +0200
"Mickael Remond" <mickael.remond@process-one.net> wrote:
> you have to tell Erlang to use the native dns resolver. Look for erl, ejabberd and inetrc on the web.
Oh, I forgot to mention I have done that. This is what my inetrc file looks like:
{lookup,["file","native"]}.
{host,{127,0,0,1}, ["localhost"]}.
{file, resolv, "/etc/resolv.conf"}.
and the rest of my system wouldn't operate too well I think, if resolv.conf wasn't set up right! When I run erlang, the arguments I pass are ( -kernel inetrc \"$TOP/etc/inetrc\" ), where $TOP/etc/inetrc is most assuredly the location of my inetrc.
Thanks for reminding me though! If it was an error with the DNS resolution thingy, is there a way I could check for that? By some small miracle my local BIND server is configured so it resolves IP addresses to what they should be.
Although... wait... If my server is @domain.com, will my own server try to resolve the name domain.com into its own IP address? Or will it only resolve domains for other servers that mine connects to? In the latter case I'm fine, but in the former case I'm in trouble because of a nasty Belkin router I'm on. It won't loop packets back to my external IP from inside the local network. Currently I have my domain name resolving to 127.0.0.1 locally, to hack around that shoddy craftsmanship, but would that mean then my ejabberd is going to report my IP address as being 127.0.0.1, to remote servers?? That would be... bad.
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived frommailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jul 09, 2006 9:50 am |
|
|
|
Guest
|
Hello,
you should check your DNS server config.
But, are you aware that to connect to another jabber server with your own:
- your server must be reachable from Internet
- the port 5269 should be open
- its public IP must be given be a resolution of your jabber domain from anywhere on the internet.
If it is not the case, a jabber server will normally reject your server connection because the dialback fails.
--
Micka |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jul 09, 2006 12:08 pm |
|
|
|
Guest
|
Op zondag 9 juli 2006 10:49, schreef Synx:
<snip>
> Although... wait... If my server is @domain.com, will my own server try to
> resolve the name domain.com into its own IP address? Or will it only
> resolve domains for other servers that mine connects to? In the latter
> case I'm fine, but in the former case I'm in trouble because of a nasty
> Belkin router I'm on. It won't loop packets back to my external IP from
> inside the local network. Currently I have my domain name resolving to
> 127.0.0.1 locally, to hack around that shoddy craftsmanship, but would that
> mean then my ejabberd is going to report my IP address as being 127.0.0.1,
> to remote servers?? That would be... bad.
I also have Dyndns and I do it like this:
* server with ejabberd and maradns on it
* My router advertise 192.168.123.3 as my primary DNS server to all LAN
computers.
* When a computer in my LAN tries to connect to devrieze.dyndns.org, maradns
tells them to contact 192.168.123.3
* On my router I have configured a rule to forward all TCP trafic for port
5269 to 192.168.123.3
HTH; if you like to know how to configure maradns, just ask (it's peace of
cake though; it's nearly as simple as configuring ejabberd, and much simplier
than configuring a mail server B-) )
--
Mvg, Sander Devrieze.
xmpp:sander@devrieze.dyndns.org
ejabberd, the expandable Jabber daemon. --
http://ejabberd.jabber.ru/
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived frommailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jul 09, 2006 11:32 pm |
|
|
|
Guest
|
On 09 Jul 2006 11:50:00 +0200
"Mickael Remond" <mickael.remond@process-one.net> wrote:
> - your server must be reachable from Internet
Check.
> - the port 5269 should be open
Open, forwarded and listening. I can usually send messages to users on other servers. It just fails intermittently, receives presence from other servers, but doesn't transmit presence.
> - its public IP must be given be a resolution of your jabber domain from anywhere on the internet.
Its... public...huh? You mean when someone on another computer requests my computer's domain name, it resolves to my public IP? That's most certainly true. Or do you mean my public IP reverse resolves to my declared domain name, which is not true?
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived frommailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Mon Jul 10, 2006 6:22 am |
|
|
|
Guest
|
Synx napisal(a):
> On 09 Jul 2006 11:50:00 +0200
> "Mickael Remond" <mickael.remond@process-one.net> wrote:
>> - its public IP must be given be a resolution of your jabber domain from anywhere on the internet.
>
> Its... public...huh? You mean when someone on another computer requests my computer's domain name, it resolves to my public IP? That's most certainly true. Or do you mean my public IP reverse resolves to my declared domain name, which is not true?
You can check at http://www.squish.net/dnscheck/ if your domain is
always possible to resolve. Sometimes DNS server above your one can be
misconfigured.
You'll get results at the end: what % of queries will / won't return
adresses.
You generally don't need a revdns... maybe only in some weird cases -
but I haven't got problems without it.
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived frommailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Mon Jul 10, 2006 9:04 am |
|
|
|
Guest
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
i have written little guide "how to" about setup srv on djbdns:
http://www.planeta.toliman.pl/?p=84
pozdrawiam,
Zbyszek Żółkiewski
Synx wrote:
> *turns off the klaxon alarms* Hey, I can't uh... afford a DNS service that provides SRV records. Can't figure out how to do them on my own either. ....
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
iD8DBQFEshfqg26u+MGPY7wRAvwOAKCFfsfzv+2ahMGoNllPE8FWQZLWBgCfdPiN
WP55hZa6Hjh9x4BouvpKEhw=
=Png4
-----END PGP SIGNATURE-----
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived frommailinglist |
|
|
| Back to top |
|
| firenzeadelaire16 |
| Posted: Fri Jun 15, 2012 11:52 pm |
|
|
|
Joined: 15 Jun 2012
Posts: 3
|
you should check your DNS server config.
But, are you aware that to connect to another jabber server with your own:
- your server must be reachable from Internet
- the port 5269 should be open
Vegas Robaina Don Alejandro |
|
|
| Back to top |
 
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
