Lookup failure for sphotos.xx.fbcdn.net

[LucidLurker]

sphotos.xx.fbcdn.net is one of the Facebook photo servers, I have been
having what I thought was broken links for at least a week now. My
lookup shows sphotos.xx.fbcdn.net as 31.13.75.26

I finally figured out that sphotos.xx.fbcdn.net doesn't resolve on
Google DNS, but does with ISP services.

When I use Google as my primary DNS, and ISP as Secondary DNS, it
fails completely. Apparently the Google DNS response causes my system
(XPpro SP3) to give up and not try the Secondary service.

I don't know what to do about the response issue, but please fix this
individual name resolution issue.

Thanks!

[Yunhong Gu]

Hello, sphotos.xx.fbcdn.net is resolving fine on Google Public DNS right now. Let us know if this still happens to you.

Yunhong

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================

[Howard]

I'm having the same problem. "It Works for Me" is not an answer.

On Feb 13, 10:04 am, Yunhong Gu <g...@google.com> wrote:
> Hello,sphotos.xx.fbcdn.netis resolving fine on Google Public DNS right

[Yunhong Gu]

Please post more details following this instruction:

http://code.google.com/speed/public-dns/docs/using.html#troubleshooting

[techn...@gmail.com]

It was only because this IP unfamiliar to me, showed up on my firewall log that I was led to this page... As you see I am using both of Googles DNS IP address's to resolve all my traffic..                                                                                                                                         2012-02-18 11:13:58 CLOSE TCP xxx.xxx.xxx.xxx 63.151.119.27 2786 80 - - - - - - - - -
2012-02-18 11:13:58 CLOSE TCP xxx.xxx.xxx.xxx 65.197.197.251 2781 80 - - - - - - - - -
2012-02-18 11:13:58 CLOSE TCP xxx.xxx.xxx.xxx 68.177.32.104 2830 80 - - - - - - - - -
2012-02-18 11:13:58 CLOSE TCP xxx.xxx.xxx.xxx 65.197.197.185 2845 80 - - - - - - - - -
2012-02-18 11:13:58 CLOSE TCP xxx.xxx.xxx.xxx 31.13.75.26 2842 80 - - - - - - - - -
2012-02-18 11:14:08 CLOSE UDP xxx.xxx.xxx.xxx 8.8.8.4 63668 53 - - - - - - - - -
2012-02-18 11:14:08 CLOSE UDP xxx.xxx.xxx.xxx 8.8.8.8 63668 53 - - - - - - - - -                                                                                               I noticed while doing an nslookup the other day that the 8.8.8.8 IP was failing to respond to the nslookup yet the 8.8.8.4 was resolving the address. As I had noticed this past week after posting two pictures back to back on Facebook which both showed at the time of posting. The next day one of the Pictures was still showing though the other was a broken link ????  It is obvious that DNS servers usually have two separate IP address's so if the first fails the second is there as backup.. It is quit possible that when Google's DNS fails and your machine resorts to your ISP's DNS address then it may very well be failing too. Truth is it kind of defeats the purpose of having two separate IP address's for a DNS server if you are only using the one address from two separate DNS services..  I use XP home SP3 Framework 3 and have a fairly large Hosts file installed as a first line means of immediately blocking traffic to certain sites. Because of its size and a known issue with Windows DNS Caching process I am forced to Disable the DNS caching service on this computer. The Hosts file allows you to assign specific IP Address's to specific Domain Names.. When blocking a Domain essentially you just assign the machines loopback or local address to the Domain Name. To allow traffic to a specific Domain you assign an actual IP address to the Domain.. I haven't actually tried this to resolve the issue you are referring to yet given my understanding of how the HOSTS file works, more or less as your machines internal DNS Server, I have no reason not to believe that by assigning the address to that specific Domain Name should resolve this issue...  This is a small piece of the HOSTS file and how you would go about doing this
# Trusted Hosts - Insert your trusted hosts with their correct IP addresses below this line.
31.13.75.26    xx-fbcdn-01-02-pao1.facebook.com
#
# 67,514 - BAD HOSTS BEGIN HERE!!!!
#
127.0.0.1    0.gvt0.com
127.0.0.1    00.eatgoogle.345.pl
127.0.0.1    00.eatgoogle.bee.pl
127.0.0.1    00.eatgoogle.bij.pl      

[Dante Díaz]

yep, i'm having the same problem.

[Paul S. R. Chisholm]

Currently, sphotos.xx.fbcdn.net. is resolving successfully from all Google Public DNS locations. The results vary from location to location (as you might expect from a name with "cdn" in it, since Content Distribution Networks often work this way). A common result:

sphotos.xx.fbcdn.net. 14 IN CNAME scontent.xx.fbcdn.net.

scontent.xx.fbcdn.net. 14 IN A 31.13.75.26

scontent.xx.fbcdn.net. 14 IN A 31.13.75.10

If anyone is still having trouble with sphotos.xx.fbcdn.net., please follow the instructions at:

  http://code.google.com/speed/public-dns/docs/using.html#troubleshooting

and specifically for this name (if you're using Windows):

tracert -d 8.8.8.8

tracert -d 8.8.4.4

nslookup -debug sphotos.xx.fbcdn.net. 8.8.8.8

nslookup -debug sphotos.xx.fbcdn.net. 8.8.4.4

Please also provide your rough geographical location: what country you're from, and optionally your subdivision / state / province within that country. (Some problems are location-specific.)

This information will help us diagnose any problems.

Thanks.  --PSRC

[bilf...@gmail.com]

It still does not resolve for me. I am in New York USA posting from Time Warner RR service.


 C:\Documents and Settings\Pathfinder>nslookup -debug sphotos.xx.fbcdn.net 8.8.8.
8
DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
*** Can't find server name for address 8.8.8.8: Timed out
Server:  UnKnown
Address:  8.8.8.8

DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 3, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 3,  authority records = 0,  additional = 0

    QUESTIONS:
        sphotos.xx.fbcdn.net, type = A, class = IN
    ANSWERS:
    ->  sphotos.xx.fbcdn.net
        canonical name = scontent.xx.fbcdn.net
        ttl = 17 (17 secs)
    ->  scontent.xx.fbcdn.net
        internet address = 31.13.78.10
        ttl = 17 (17 secs)
    ->  scontent.xx.fbcdn.net
        internet address = 31.13.69.42
        ttl = 17 (17 secs)

------------
Non-authoritative answer:
Name:    scontent.xx.fbcdn.net
Addresses:  31.13.78.10, 31.13.69.42
Aliases:  sphotos.xx.fbcdn.net

[Miss Stasha]

I'm having the same issue and have had it since FB switched to
Timeline. I'm in California.

[Paul S. R. Chisholm]

Yep; see other thread in this forum. Root cause is a Facebook
nameserver error; I'm working around it now.

The bad response from Facebook's nameservers should only be cached for
one second on Google Public DNS's servers (though it can be
re-cached). Try waiting a minute and refreshing.

Hope my workaround helps soon. --PSRC (software engineer, Google Public DNS)

Note: The output you pasted into your reply (and thank you for it)
shows a successful name resolution. It's a sporadic problem.

On Sat, Feb 25, 2012 at 4:23 PM, <bilf...@gmail.com> wrote:
> It still does not resolve for me. I am in New York USA posting from Time
> Warner RR service.
>
>
>  C:\Documents and Settings\Pathfinder>nslookup -debug sphotos.xx.fbcdn.net

[Paul S. R. Chisholm]

The Google Public DNS team has put a workaround into place that should
prevent this problem from recurring.

Really (but confidently) hope this helps. --PSRC

[julia...@gmail.com]

I fixed mine in FB. In FB, click on the down arrow next to "Home". Then click on "Account Settings". Now on the left click "Security". Now back on the right click on "Secure Browsing". Now select "Browse Facebook on a secure connection (https) when possible" and click "save changes". You should be good to go.

Hope this helps

[Seth Robison]

this worked for me. been bugging me for months now and finally a
solution that works. thanks a lot

[MinJae Hwang]

Hello Patty,

I've tried to resolve sphotos-a.xx.fbcdn.net from every Google Public DNS Server and it seems it works fine for now.

For further investigation, could you do the following and report back to this forum? It will be very helpful to resolve the issue.

https://developers.google.com/speed/public-dns/docs/using#troubleshooting

Thanks,

MinJae Hwang

On Sat, Jul 14, 2012 at 11:15 PM, <pattyg...@gmail.com> wrote:

I have been having this same problem for over a week now...........................any ideas how to fix ?  

The server at sphotos-a.xx.fbcdn.net can't be found, because the DNS lookup failed 

thanks, patty