Ustream not working

2010-09-21 09:04:11 pm

When I'm the w00ty page showing who's streaming, I can see who is streaming but I can't see what they're streaming. And whenever I click on the link to that stream, it takes me to some domain ad page. Any time I go to something with ustream.tv in the address I get that page. Anyone know what's going on?

This is the screen shot when I'm on the w00ty page
http://img694.imageshack.us/img694/1856/ustreamm.png

This is the screen shot of the ad page
http://img833.imageshack.us/img833/7615/streamtv.png

Thread title:

Zyre

2010-09-21 09:14:40 pm

The Speedrunning Teacher

Either Ustream is doing a major overhaul, or something else. That ad page is the company that his hosting Ustream's website.

Something915

2010-09-21 09:19:55 pm

Is this happening to anyone else?

Zyre

2010-09-21 09:22:47 pm

The Speedrunning Teacher

Happened to me, and a few people in the IRC mentioned it as well. So, no, you're not alone on this.

Something915

2010-09-21 09:26:51 pm

So, I just have to wait it out? Guess I can do that.

Zyre

2010-09-21 09:42:10 pm

The Speedrunning Teacher

It's back up now.

Something915

2010-09-21 09:52:51 pm

It's still doing it too me

Darkwing Duck

2010-09-21 09:53:09 pm

Highly Evolved

Quote from Zyre:

It's back up now.

Liar!

Zyre

2010-09-21 09:58:46 pm

The Speedrunning Teacher

Weird, did you try clearing your browser's cache? It's up for me.

Something915

2010-09-21 10:02:09 pm

Yea, I've done all that.

Zyre

2010-09-21 10:22:34 pm

The Speedrunning Teacher

Quote from Darkwing Duck:

Quote from Zyre:

It's back up now.

Liar!

I take it back, seems Ustream is having issues tonight. Too many users accessing it, maybe?

PJ

2010-09-21 10:46:01 pm

Is PJ

Problem iz hear also

bmn

Edit history:

bmn: 2010-09-22 09:03:35 am

bmn: 2010-09-22 08:43:54 am

2010-09-22 08:31:29 am

I for one haven't had any issues. What I'd guess is that one of Ustream's 13 (!) nameservers somehow got incorrect records pointing to the domain registrar, or a new nameserver was added to the list (say, the registrar's own servers) before it actually got the correct records.

What's then happened (assuming something like this did happen) is that your DNS host (likely your ISP) timed out on the records (which is normal), contacted the main registrar database, and randomly selected the rogue nameserver as the one it would query. That means it's just a case of luck whether you get screwed or not, and you then have to wait for the next DNS refresh.

The Time To Live is only 30 minutes, but DNS has big issues with caching at multiple points. On your own system (assuming Windows), you can run this command from Run: ipconfig /flushdns which will clear your own DNS cache. If it's the ISP's side, you'll just get the bad record again. In that case, I'd suggest looking at a third-party DNS provider like OpenDNS. Setting that up is just a case of finding your network connection in the control panel, going into the TCP/IP settings, and changing the DNS like below. Then you flush the DNS as explained above.

Quote from Zyre:

That ad page is the company that his hosting Ustream's website.

Hosting Ustream's domain, there's a difference.

The deal with DNS is that any server can be set up to appropriately handle a visit to ustream.tv (or any other domain). It's the nameservers (that are configured by Ustream's admins) that decide which server to go to.

The domain registrar's "parking" servers (which serve the "coming soon" pages like the one that's appearing for some on Ustream) use wildcard domain configuration, which means that a visit to any domain is handled by exactly the same code, and they just subsitute the domain name into the template they use. Ustream's servers are working fine, but you've been sent to the wrong computer, so you get a wildly different page.

I for one haven't had any issues. What I'd guess is that one of Ustream's 13 (!) nameservers somehow got incorrect records pointing to the domain registrar, or a new nameserver was added to the list (say, the registrar's own servers) before it actually got the correct records.

What's then happened (assuming something like this did happen) is that your DNS host (likely your ISP) timed out on the records (which is normal), contacted the main registrar database, and randomly selected the rogue nameserver as the one it would query. That means it's just a case of luck whether you get screwed or not, and you then have to wait for the next DNS refresh.

The Time To Live is only 30 minutes, but DNS has big issues with caching at multiple points. On your own system (assuming Windows), you can run this command from Run: [b]ipconfig /flushdns[/b] which will clear your own DNS cache. If it's the ISP's side, you'll just get the bad record again. In that case, I'd suggest looking at a third-party DNS provider like [url=http://opendns.com]OpenDNS[/url]. Setting that up is just a case of finding your network connection in the control panel, going into the TCP/IP settings, and changing the DNS like below. Then you flush the DNS as explained above.

[quote="Zyre"]That ad page is the company that his hosting Ustream's website.[/quote]
Hosting Ustream's domain, there's a difference.

The deal with DNS is that [i]any[/i] server can be set up to appropriately handle a visit to ustream.tv (or any other domain). It's the nameservers (that are configured by Ustream's admins) that decide [i]which[/i] server to go to.

The domain registrar's "parking" servers (which serve the "coming soon" pages like the one that's appearing for some on Ustream) use wildcard domain configuration, which means that a visit to any domain is handled by exactly the same code, and they just subsitute the domain name into the template they use. Ustream's servers are working fine, but you've been sent to the wrong computer, so you get a wildly different page.

bmn

2010-09-22 08:44:18 am

OpenDNS setup:

Attachment:

opendns.png