Facebook is IPv6-enabled now – without a whitelist

UPDATE 22 May 2012

It looks as though Facebook is now 100% IPv6-enabled, without white-list filtering!  See the dig below:

The Updated Dig

mylaptop:~$ dig @8.8.8.8 AAAA www.facebook.com

; <<>> DiG 9.8.1-P1 <<>> @8.8.8.8 AAAA www.facebook.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36329
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.facebook.com.        IN    AAAA

;; ANSWER SECTION:
www.facebook.com.    50    IN    AAAA    2a03:2880:2110:3f02:face:b00c::

;; Query time: 33 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue May 22 21:21:11 2012
;; MSG SIZE  rcvd: 62

Ahead of the World IPv6 Launch schedule for June 6, 2012, it seems that Facebook has enabled its website www.facebook.com for IPv6.  However, here’s the catch: it is only reachable for networks on Google’s White List program (see information on that here: http://www.google.com/intl/en/ipv6/).  Don’t believe me?  Take a look at some “dig” snapshots from our network (we are on Google’s IPv6 White List) and one from Google’s own public DNS server (8.8.8.8).  This is some good stuff!  Bring on the rest, but let’s make it totally available to everyone else!

The Dig

From Google’s Public DNS Server:

mylaptop:~$ dig @8.8.8.8 AAAA www.facebook.com
; <<>> DiG 9.7.3 <<>> @8.8.8.8 AAAA www.facebook.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29667
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.facebook.com. IN AAAA
;; AUTHORITY SECTION:
www.facebook.com. 369 IN SOA glb1.facebook.com. dns.facebook.com. 2008111138 10800 3600 604800 86400
;; Query time: 21 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Apr 28 16:16:27 2012
;; MSG SIZE rcvd: 79

From my DNS Server on Google’s IPv6 White List:

mylaptop:~$ dig AAAA www.facebook.com
; <<>> DiG 9.7.3 <<>> AAAA www.facebook.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43197
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0
;; QUESTION SECTION:
;www.facebook.com. IN AAAA
;; ANSWER SECTION:
www.facebook.com. 39 IN AAAA 2620:0:1c18:0:face:b00c:0:1
;; AUTHORITY SECTION:
facebook.com. 95467 IN NS ns3.facebook.com.
facebook.com. 95467 IN NS ns4.facebook.com.
facebook.com. 95467 IN NS ns5.facebook.com.
;; Query time: 7 msec
;; SERVER: 10.0.0.150#53(10.0.0.150)
;; WHEN: Sat Apr 28 16:16:38 2012
;; MSG SIZE rcvd: 116

The Browser Proof

 

2 thoughts on “Facebook is IPv6-enabled now – without a whitelist”

  1. This is strange. I change my internet connection and on my main home net work Facebook shows up as 2a03:2880:2110:3f02:face:b00c::

    However on my router it shows when I switch to that as 69.171.228.70

    If you can tell me how to change Facebook back to showing as 69.171.228.70 I would appreciate that because it didn’t always show up as 2a03:2880:2110:3f02:face:b00c:: because before it was 69.171.228.70

    I understand that the article explained the change, I’d just appreciate an explanation or a confirmation of a way of changing it back.

    1. Jared-

      Looks like you were the beneficiary of an IPv6 deployment on your network. This is a good thing! Why would you want to change it back? Who is your service provider?

Comments are closed.

Scroll to Top