#1038 closed request (invalid)
Reaching jabber.org
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | tbd | Milestone: | ietf-097 |
Component: | incoming | Keywords: | |
Cc: | My Current Location: | ||
My MAC Address: | My OS: |
Description
[Changed subject and added NOC via BCC to meeting tickets alias] OK. Now jabber doesn't seem to resolve in my DNS. Is this the SK DNS and filtering problem discussed at the weekend? Adrian From: Tim Chown [mailto:Tim.Chown@jisc.ac.uk] Sent: 15 November 2016 08:55 To: adrian@olddog.co.uk Cc: Rosen, Brian; Dan Romascanu; 97attendees@ietf.org Subject: Re: [97attendees] meetecho from remote participant perspective That’s what I’ve been seeing too. Tim On 15 Nov 2016, at 08:23, Adrian Farrel <adrian@olddog.co.uk> wrote: While <http://jabber.org/> jabber.org has been resolving today, I have been unable to reach it in any way. Had to move to another account. Adrian From: Tim Chown [mailto:Tim.Chown@jisc.ac.uk] Sent: 15 November 2016 08:15 To: Rosen, Brian Cc: Dan Romascanu; adrian@olddog.co.uk; 97attendees@ietf.org Subject: Re: [97attendees] meetecho from remote participant perspective My Jabber client has had significant problems connecting today. It was OK yesterday. I’ve not reported it though as Meetecho does everything in one view (chat, slides and video). Not sure about deprecating it, as Jabber + audio is a more lightweight way to participate remotely. Would be interesting to see the stats though.
Change history (4)
comment:1 Changed 4 years ago by
comment:2 Changed 4 years ago by
Owner: | changed from llynch@… to rob@… |
---|---|
Status: | new → assigned |
comment:3 Changed 4 years ago by
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Additionally we are returning the same response as 8.8.8.8, 4.2.2.2 and others. So we are actually doing the right thing. Hopefully the delegation issues from org to jabber.org shown in the DNSVIZ link (provided by Jim in the last comment) for jabber.org can be resolved quickly on that end. Sorry that it doesn't seem to be something we can help with.
As we don't appear to have an issue on our end, I am going to close this ticket. But if you disagree with our assessment of the situation and want to comment or re-open this ticket please feel free to do so, and just let us know what you think we could do to help you resolve the issue.
Thanks,
Rob aka alice
Check out http://dnsviz.net/d/jabber.org/dnssec/
It sure seems sick to me, and definitely not a IETF Network related issue...
-Jim