[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Jabber server not working?

To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Jabber server not working?
From: Simon Leinen <simon@limmat.switch.ch>
Date: Mon, 14 Jul 2003 16:52:57 +0200
Date: Tue, 15 Jul 2003 07:20:34 +0000
Cc: hartmans@mit.edu (Sam Hartman), wgchairs@ietf.org
In-reply-to: <p06001a09bb3841da70d8@[129.46.76.141]>
References: <20030714111250.0F2B7151D35@konishi-polis.mit.edu><p06001a09bb3841da70d8@[129.46.76.141]>

Pete Resnick writes:
> On 7/14/03 at 7:12 AM -0400, Sam Hartman wrote:
>> I seem to get an error joining conferences on
>> conference.ietf.jabber.com.  Is this the right server?

> Use ietf.jabber.com.

I'm having trouble logging into ietf.jabber.com from the IETF wireless
LAN.  My client pops up an error message saying "Disconnected:
Couldn't Resolve Hostname".

Assuming this comes from the server, it may have to do with the lack
of DNS inverse mappings for the address space used at the meeting.
-- 
Simon.

$ dig ptr -x 81.160.161.185

; <<>> DiG 9.2.2 <<>> ptr -x 81.160.161.185
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47736
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;185.161.160.81.in-addr.arpa.   IN      PTR

;; AUTHORITY SECTION:
160.81.in-addr.arpa.    120     IN      SOA     ns1.ietf57.telekom.at. admin.ietf57.telekom.at. 200311484 600 10 1200 300

;; Query time: 67 msec
;; SERVER: 81.160.16.1#53(81.160.16.1)
;; WHEN: Mon Jul 14 16:52:35 2003
;; MSG SIZE  rcvd: 108

References:
- Re: Jabber server not working?
  - From: Pete Resnick <presnick@qualcomm.com>

Prev by Date: Re: suggestion for problem statement
Next by Date: Re: Jabber server not working?
Previous by thread: Re: Jabber server not working?
Next by thread: Re: Jabber server not working?
Index(es):
- Date
- Thread