Description
Starting in the last few days, we’ve noticed a large uptick in the Web SDK attempting to connect to urls with missing DNS records.
From my understanding, the Web SDK makes an API request to retrieve meeting information and receives in the response some regional endpoints used when setting up the meeting. We’ve started seeing errors for the following domains:
zoomiad94rwg.iad.zoom.us
zoomiad93rwg.iad.zoom.us
zoomiad10rwg.iad.zoom.us
dig shows that these domains are missing A records:
$ dig +short zoomiad94rwg.iad.zoom.us A
Testing locally, all the domains the SDK has attempted to use resolve as expected, for example:
$ dig +short zoomnxs151rwg.nx.zoom.us A
147.124.111.151
Obviously this is causing a pretty negative user experience for our users. Any chance these spurious domains could be fixed or removed from the rotation? Thanks.
Error?
We see this (redacted) error in the browser console:
WebSocket connection to 'wss://zoomiad94rwg.iad.zoom.us/wc/api/XXX?...' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Still occurring as of a few moments ago. (I’m attempting to make it through the sales labyrinth for “Premier Dev Support” to see if I can talk to someone… until then I’ll keep this thread fresh as this is a pretty impactful production outage).
Thanks for contacting your backend engineers @donte.zoom. It appears that this has grown into an even more serious issue, which @ryan has helpfully flagged in his new forum post.
It appears that even Zoom’s own website is broken, in that if you go to a meeting (e…g, Launch Meeting - Zoom), and click on the bottom “Join from Your Browser”, it doesn’t load.
Since Zoom’s own website is broken, this issue is definitely not due to any 3rd-party developers not fully understanding how to implement the SDK. Could you please ask the backend engineers to fix this problem as soon as possible? We rely extensively on the SDK for our educational technology service, and this is a severe breakage. Thank you!
