This morning I am very frequently getting an error because my computer can't find "apps.facebook.com". Is there something wonky happening with DNS?
Offline
its been happening for the last like 4 days.
Offline
It's much worse today than I have ever seen it before. I am in San Francisco now, but usually I am in Vancouver... wonder if maybe that makes a difference.
Offline
still not getting through at all. watching my server logs I can see that lots of people are using my app, so at least the problem isn't universal. ![]()
Offline
Ohh, my Facebook url just changed back to facebook.com, not new.facebook.com
I think everything should smoothen out after the DNS changes are final. Everything is running smooth for me now. Facebook is starting to feel like home again! Woot!
Last edited by DesignerMichael (2008-10-04 14:12:42)
Offline
Still happening to me ![]()
Offline
open command prompt do a ipconfig /flushdns hit enter.
Offline
FACEBOOK STAFF - PLEASE TAKE NOTICE
You clearly have a DNS propagation issue with your CNAME record for apps.new.facebook.com...
I'm sporadically getting one of the following responses (note that I'm flushing my DNS cache between each request).
============================================
$ nslookup apps.new.facebook.com
Server: 68.87.71.226
Address: 68.87.71.226#53
** server can't find apps.new.facebook.com: NXDOMAIN
$ nslookup apps.new.facebook.com
Server: 68.87.71.226
Address: 68.87.71.226#53
Non-authoritative answer:
apps.new.facebook.com canonical name = apps.facebook.com.
Name: apps.facebook.com
Address: 69.63.178.19
============================================
This is completely unacceptable. I've been experiencing this for several days, and its causing issues not only for my application, but for its users. The fact that this has been brought up all over the place (not only by developers but users as well), and still been wholly unaddressed (not even acknowledged) by facebook staff is ridiculous. There's an obvious problem here, and its affecting just about everyone that's trying to use applications.
Offline
Oh my god, this is ridiculous...
I have to switch back and forth between apps.facebook.com and apps.new.facebook.com every 5 minutes to access my app... My users are also complaining! From last weeks platform slowdown and crash... To this! !!!
Last edited by DesignerMichael (2008-10-04 22:33:09)
Offline
ersingencturk wrote:
open command prompt do a ipconfig /flushdns hit enter.
on mac os x 10.5 the following command does the same thing:
dscacheutil -flushcache
Offline
What about our users? Grrr...
Offline
same, this is weak
Offline
Thats weird, it seems to work fine here. I think I had issues with it for 10 seconds all of today.
Offline
Think this is not gonna have consequences? Guess what application is not working...
VOTE FOR CHANGE
The page you requested was not found.
You may have clicked an expired link or mistyped the address. Some web addresses are case sensitive.
* Return home
* Go back to the previous page
The registration deadline this MONDAY for many states in the US. Not good, especially for a campaign with such power on this Platform.
Offline
I'm having the same issue. Between this and the users_getInfo bug my work is at a standstill....
Offline
linademartinez wrote:
Think this is not gonna have consequences? Guess what application is not working...
VOTE FOR CHANGEThe page you requested was not found.
You may have clicked an expired link or mistyped the address. Some web addresses are case sensitive.
* Return home
* Go back to the previous pageThe registration deadline this MONDAY for many states in the US. Not good, especially for a campaign with such power on this Platform.
This has been announced by Facebook for 1-2 weeks, remove the .new subdomain and it works fine.
Offline
cyMall, your misnformation isn't helping.
apps.facebook.com is/was screwed up as well.
In fact, frequently, the only way I could get an app to work was change it to apps.new.facebook.com
Offline
I blogged about this here: http://staynalive.com/articles/2008/10/ … rl-change/ - note that Techmeme still hasn't recognized this as news (not that they catch much real news anyway).
Offline
I also experienced the issue yesterday. But now its working fine for me.
Offline
it's definitely not very cool of facebook to remove the apps.new subdomain without warning.
they should at least have had a crossover period of redirecting from apps.new to apps. (i.e. the inverse of what they were doing during the preview phase).
Also, why pick a weekend (when many of us aren't around to help our users out) to make such a drastic (and unannounced) change?
Last edited by mikep (2008-10-06 09:38:58)
Offline
friendhugs wrote:
cyMall, your misnformation isn't helping.
apps.facebook.com is/was screwed up as well.
In fact, frequently, the only way I could get an app to work was change it to apps.new.facebook.com
Odd, nothing works on apps.new.facebook.com, everyone I know is getting a Page not Found error.
Offline
mikep wrote:
it's definitely not very cool of facebook to remove the apps.new subdomain without warning.
they should at least have had a crossover period of redirecting from apps.new to apps. (i.e. the inverse of what they were doing during the preview phase).
Also, why pick a weekend (when many of us aren't around to help our users out) to make such a drastic (and unannounced) change?
This was their warning from Sept 24th
Switching over api.facebook.com
Sep 24, 2008 3:35pm
As the final users switch over to the new facebook site, we are going to transition the url scheme back to facebook.com from new.facebook.com. With this change, we are also going to stop supporting the old api currently hosted on api.facebook.com.
Starting next week, api.facebook.com and api.new.facebook.com will both host the new api. Going forward we will continue to mirror api.new.facebook.com for ease of use.
For details on migrating applications to the new api, see http://wiki.developers.facebook.com/ind … tion_Guide for more details.
Offline
cyMall wrote:
This was their warning from Sept 24th
Switching over api.facebook.com
Sep 24, 2008 3:35pm
As the final users switch over to the new facebook site, we are going to transition the url scheme back to facebook.com from new.facebook.com. With this change, we are also going to stop supporting the old api currently hosted on api.facebook.com.
Starting next week, api.facebook.com and api.new.facebook.com will both host the new api. Going forward we will continue to mirror api.new.facebook.com for ease of use.
For details on migrating applications to the new api, see http://wiki.developers.facebook.com/ind … tion_Guide for more details.
Totally agree with you Francis. But what good is it if users have no idea?
Update sent to over two MILLION Obama supporters just this Saturday:
URGENT: Registration Deadline
Sat 1:37pm
The registration deadline in many states is MONDAY. You don't have any time to waste. In order to vote in this year's election, you need to get registered now.
http://apps.new.facebook.com/obama
If you're already registered, take the time to remind your friends in key states. Every single vote is going to matter this fall.
http://apps.new.facebook.com/obama/recruit
Remind your Facebook friends and get registered today!
Offline
linademartinez wrote:
Totally agree with you Francis. But what good is it if users have no idea?
Update sent to over two MILLION Obama supporters just this Saturday:URGENT: Registration Deadline
Sat 1:37pm
The registration deadline in many states is MONDAY. You don't have any time to waste. In order to vote in this year's election, you need to get registered now.
http://apps.new.facebook.com/obama
If you're already registered, take the time to remind your friends in key states. Every single vote is going to matter this fall.
http://apps.new.facebook.com/obama/recruit
Remind your Facebook friends and get registered today!
Thats horrible, I think I got lucky by seeing that. But usually when I see such reports I just act upon them knowing that bugs will occur when they say they will continue to use a work around. But its horrible for that application to use those links :S
I guess I never noticed the DNS issue because I am using a backup DNS provider in case mine would ever crash or pages don't load. You guys should use something like OpenDNS and setup redundancy.
Offline