- Test - lists.nanog.org

AAAA's for www.netflix.com
by Frank Bulk 08 Jun '12

08 Jun '12

I started monitoring IPv6 access to www.netflix.com after seeing this posting (http://www.personal.psu.edu/dvm105/blogs/ipv6/2012/06/netflix-is-back.html) and what I found, over the week, was that access was coming and going (www.premieronline.net/~fbulk/netflix.png) But not because of IPv6 connectivity, but because the AAAA's were coming and going. Netflix's DNS TTL is pretty short. I assume Netflix has some global DNS load balancing so my perspective may not be complete. Has anyone else been seeing this? I contacted a Netflix employee (he's well known on this list) and he responded once but I haven't heard back since Saturday. Here's some sample queries from Saturday and today. ========================================================= nagios:/home/fbulk# dig AAAA www.netflix.com ; <<>> DiG 9.7.3 <<>> AAAA www.netflix.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26825 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.netflix.com. IN AAAA ;; AUTHORITY SECTION: netflix.com. 150 IN SOA dns.netflix.com. nicadmin.netflix.com. 2012060104 900 600 1209600 1800 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sat Jun 2 09:29:17 2012 ;; MSG SIZE rcvd: 82 nagios:/home/fbulk# ========================================================= ========================================================= nagios:/home/fbulk# dig AAAA www.netflix.com ; <<>> DiG 9.7.3 <<>> AAAA www.netflix.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33117 ;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 8, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.netflix.com. IN AAAA ;; ANSWER SECTION: www.netflix.com. 132 IN CNAME dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. 12 IN AAAA 2406:da00:ff00::3210:e195 dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. 12 IN AAAA 2406:da00:ff00::3213:5282 dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. 12 IN AAAA 2406:da00:ff00::3213:6340 dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. 12 IN AAAA 2406:da00:ff00::3213:779a dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. 12 IN AAAA 2406:da00:ff00::1715:75cd dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. 12 IN AAAA 2406:da00:ff00::1715:eceb dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. 12 IN AAAA 2406:da00:ff00::1717:e388 dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com. 12 IN AAAA 2406:da00:ff00::1717:eb58 ;; AUTHORITY SECTION: elb.amazonaws.com. 7092 IN NS ns-916.amazonaws.com. elb.amazonaws.com. 7092 IN NS ns-941.amazonaws.com. elb.amazonaws.com. 7092 IN NS ns-927.amazonaws.com. elb.amazonaws.com. 7092 IN NS ns-925.amazonaws.com. elb.amazonaws.com. 7092 IN NS ns-934.amazonaws.com. elb.amazonaws.com. 7092 IN NS ns-935.amazonaws.com. elb.amazonaws.com. 7092 IN NS ns-944.amazonaws.com. elb.amazonaws.com. 7092 IN NS ns-947.amazonaws.com. ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sat Jun 2 09:34:35 2012 ;; MSG SIZE rcvd: 504 nagios:/home/fbulk# ========================================================= ========================================================= nagios:/home/fbulk# dig AAAA www.netflix.com ; <<>> DiG 9.7.3 <<>> AAAA www.netflix.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34529 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.netflix.com. IN AAAA ;; AUTHORITY SECTION: netflix.com. 94 IN SOA dns.netflix.com. nicadmin.netflix.com. 2012060107 900 600 1209600 1800 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Jun 6 09:00:44 2012 ;; MSG SIZE rcvd: 82 nagios:/home/fbulk# ========================================================= Frank Bulk

7 14

sporadic IPv6 connectivity to forums.comcast.com
by Casey Deccio 08 Jun '12

08 Jun '12

I'm seeing sporadic IPv6 connectivity issues to forums.comcast.com: casey@rome$ curl -I6 forums.comcast.com HTTP/1.1 200 OK Date: Thu, 07 Jun 2012 21:48:37 GMT [snip...] casey@rome$ curl -I6 forums.comcast.com curl: (7) couldn't connect to host casey@rome:~$ traceroute6 forums.comcast.com traceroute to forums.comcast.com (2620:6a:8000:4::11) from 2001:470:21:31::adf5:492a, port 33434, from port 42309, 30 hops max, 60 byte packets 1 2001:470:21:31::1 (2001:470:21:31::1) 1.713 ms 1.922 ms 2.039 ms 2 2001:470:1f:b::1 (2001:470:1f:b::1) 10.575 ms 3.343 ms 3.147 ms 3 10gigabitethernet1-1.core1.sjc1.he.net (2001:470:1:7c::1) 6.855 ms 4.225 ms 4.252 ms 4 10gigabitethernet2-1.core1.sjc2.he.net (2001:470:0:55::2) 4.271 ms 14.442 ms 4.469 ms 5 sjo-eqx-s1-link.telia.net (2001:2000:3080:1b7::1) 5.385 ms 4.669 ms 4.434 ms 6 internap-ic-140172-sjo-bb1.c.telia.net (2001:2000:3080:17f::2) 4.702 ms 4.803 ms 4.848 ms 7 border1-bbnet2.sje.pnap.net (2600:c02:0:102::1:1) 5.175 ms 25.023 ms 4.808 ms 8 lithiumtechinc-2.border1.sje.pnap.net (2600:c02:1001:3::2) 9.445 ms 8.120 ms 7.804 ms 9 2620:6a:8000:4::11 (2620:6a:8000:4::11) 5.491 ms 5.712 ms 5.873 ms casey@rome:~$ traceroute6 forums.comcast.com traceroute to forums.comcast.com (2620:6a:8000:4::11) from 2001:470:21:31::adf5:492a, port 33434, from port 42311, 30 hops max, 60 byte packets 1 2001:470:21:31::1 (2001:470:21:31::1) 1.574 ms 1.514 ms 1.856 ms 2 2001:470:1f:b::1 (2001:470:1f:b::1) 2.882 ms 3.089 ms 14.462 ms 3 10gigabitethernet1-1.core1.sjc1.he.net (2001:470:1:7c::1) 4.573 ms 4.466 ms 6.683 ms 4 10gigabitethernet2-1.core1.sjc2.he.net (2001:470:0:55::2) 4.525 ms 10.401 ms 4.748 ms 5 sjo-eqx-s1-link.telia.net (2001:2000:3080:1b7::1) 4.794 ms 4.931 ms 4.406 ms 6 internap-ic-140172-sjo-bb1.c.telia.net (2001:2000:3080:17f::2) 4.837 ms 4.922 ms 4.527 ms 7 border1-bbnet1.sje.pnap.net (2600:c02:0:101::1:1) 5.884 ms 4.626 ms 5.037 ms 8 border3-bbnet2.sje.pnap.net (2600:c02:0:102::1:3) 3157.850 ms !H 3270.481 ms !H 3226.411 ms !H Is this perhaps a routing issue? Casey

2 1

AT&T Bucks IPv6 Trend
by Henry Linneweh 07 Jun '12

07 Jun '12

Since AT&T has not said much about ipv6, here is their position on it and how they intend to deploy http://www.lightreading.com/blog.asp?blog_sectionid=847&doc_id=221739&f_src… -Henry

1 0

IX in France
by Ido Szargel 07 Jun '12

07 Jun '12

Hi All, We are currently looking to connect to one of the IX's available in Paris, It seems that there are 2 "major" players - FranceIX and Equinix FR, can anyone share their opinions about those? Thanks, Ido

10 11

IPv6 on AWS
by Grant Ridder 07 Jun '12

07 Jun '12

Hi, Is there anyone here from Amazon that knows when Amazon Web Services will support native IPv6? Thanks, Grant

1 0

Configuration Systems
by Andrew Latham 07 Jun '12

07 Jun '12

Lurker speaking... beware... I have been talking with some folks from various industries about configuration systems ala Bcfg2, Puppet, Chef, and others. Many of them care far too much about the current nodes configuration status as some admin had logged in and changed something. I am authoring a system called Enablement that uses what ever technology needed (ssh, telnet over admin vlan, rsh, etc...) to push a planned system/config to the device. Monitoring and auditing are all the same at the moment as we need historical data on when a service or port started and stopped offering its planned or unplanned service. For a meeting Thursday I am looking forward to the future of configuring systems. My idea is push + netblock scanning of services. With stacks for clouds we can startup and shut down nodes easy. Would a bend over backwards config reader for all the "Configuration Management Systems" be the best medium ground from the service provider point of view? Enablement.... Send another man to fight on the front line. -- ~ Andrew "lathama" Latham lathama(a)gmail.com http://lathama.net ~

1 0

.GW registrar?
by Ben Carleton 06 Jun '12

06 Jun '12

Hello all, Does anyone have a contact at either DENIC or "Fundação IT & MEDIA Universidade de Bissao" that can advise if registrations are currently being accepted for .GW domain names? The IANA admin contact, admin(a)register.gw, is at a domain with no valid MX records (or A records, for that matter). The technical contact is listed as DENIC. TIA, -- Ben Carleton

3 3

Re: IPv6 /64 links (was Re: ipv6 book recommendations?)
by Owen DeLong 06 Jun '12

06 Jun '12

On Jun 6, 2012, at 1:02 PM, Steve Clark wrote: > On 06/06/2012 03:05 PM, Owen DeLong wrote: >> >> It is because of IEEE EUI-64 standard. >> >> It was believed at the time of IPv6 development that EUI-48 would run out of >> numbers and IEEE had proposed going to EUI-64. While IEEE still hasn't >> quite made that change (though Firewire does appear to use EUI-64 already), >> it will likely occur prior to the EOL for IPv6. >> >> There is a simple algorithm used by IEEE for mapping EUI-48 onto the EUI-64 >> space. >> >> The 0x02 bit of the first octet of an EUI-64 address is an L-Flag, indicating that >> the address was locally generated (if it is a 1) vs. IEEE/vendor assigned (if it is a 0). >> >> The mapping process takes the EUI-48 address XX:YY:ZZ:RR:SS:TT and maps >> it as follows: >> >> let AA = XX xor 0x02. >> >> AAYY:ZZff:feRR:SSTT >> >> ff:fe above is literal. >> >> IPv6 was originally going to be a 32-bit address space, but, the developers > did you mean "originally going to be a 64-bit address space"... Uh, yeah... Sorry... Brain fart. Originally a 64-bit address space. Owen

1 0

seeking older .com / .net zone files
by Manish Karir 06 Jun '12

06 Jun '12

All, We are working on a project with the University of Michigan related with studying the evolution of .com/.net zones Does anyone have copies of .com / .net zone files around the beginning of 2011? Any help would be greatly appreciated. Thanks. -manish

2 1

RFC5549
by Aris Lambrianidis 06 Jun '12

06 Jun '12

Hello all, In light of World IPv6 Launch day, I would like to raise awareness for RFC5549, "Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop" (http://tools.ietf.org/html/rfc5549) As far as I'm aware of, this RFC has yet to be implemented by any vendors so far but it could help massively in the increasing scenarios where IPv4 addressing is scarce. This includes many IXPs which invariably will sooner or later run into this problem. If you happen to be attending the last day of NANOG, I'd be happy to talk to you in person about this for further details (I'm the dude with "RFC5549" written on the back of his laptop). Aris Lambrianidis, AMS-IX

1 0