Unless it's an OpenConnect appliance on an upstream or peer's network.
----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP ----- Original Message ----- From: "Ken Hohhof" <af...@kwisp.com> To: "AnimalFarm Microwave Users Group" <af@af.afmug.com> Sent: Tuesday, October 16, 2018 10:13:59 AM Subject: Re: [AFMUG] Tracking Down DualStack Problems I do like the fact that most of the time they are using their own IP space and it has rDNS to nflxvideo.net, unlike a lot of CDN traffic which could be anything and probably has no rDNS. From: AF <af-boun...@af.afmug.com> On Behalf Of Mike Hammett Sent: Tuesday, October 16, 2018 8:12 AM To: AnimalFarm Microwave Users Group <af@af.afmug.com> Subject: Re: [AFMUG] Tracking Down DualStack Problems Of everyone in the CDN space, Netflix is the worst to deal with. ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP ----- Original Message ----- From: "Erich Kaiser" < er...@northcentraltower.com > To: "AnimalFarm Microwave Users Group" < af@af.afmug.com > Sent: Monday, October 15, 2018 9:01:19 PM Subject: Re: [AFMUG] Tracking Down DualStack Problems There is no Netflix peering available in SLC, hence why we have a Cache box there. BTW we support Ipv6 :) Sterling hit me up if interested in bandwidth in SLC. I will give you a good deal! On Mon, Oct 15, 2018 at 8:08 PM Mike Hammett via AF < af@af.afmug.com > wrote: Looks like SLIX needs to put some effort into getting more content there. ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP From: "Sterling Jacobson" < sterl...@avative.net > To: "AnimalFarm Microwave Users Group" < af@af.afmug.com > Sent: Monday, October 15, 2018 1:20:51 PM Subject: Re: [AFMUG] Tracking Down DualStack Problems Sort of. I get from Syriga and from a data center that has blended upstream including the SLC IX. Not sure if the IPv6 uses the IX much. One of my upstreams doesn’t BGP my IPv6 yet, so it’s just the Datacenter for the IPv6. That datacenter is connected directly to main colocation facilities in LA, San Jose, Seattle, Toronto, Virginia and others, so I often hit CDNs out in those colo’s instead of downtown SLC. Not sure that’s a bad thing, but it’s interesting and makes CDN streaming tracking a bit difficult as others have stated. From: AF < af-boun...@af.afmug.com > On Behalf Of Mike Hammett Sent: Monday, October 15, 2018 11:44 AM To: AnimalFarm Microwave Users Group < af@af.afmug.com > Subject: Re: [AFMUG] Tracking Down DualStack Problems Where do you get your upstream from? Any IXes? ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP From: "Sterling Jacobson" < sterl...@avative.net > To: "AnimalFarm Microwave Users Group" < af@af.afmug.com > Sent: Monday, October 15, 2018 12:20:12 PM Subject: Re: [AFMUG] Tracking Down DualStack Problems I’ve noticed this dual stack problem as well. Delays and IPv6 routes not optimized like IPv4, buffering and general issues as well. Long page loads as computers and devices search for IPv6 and get ghosted or timed out switching to IPv4. I mean I don’t even think eBay is IPv6 yet, for example. I could be wrong on that, but it seems to always go IPv4 by default and it’s the same on lots of sites still. For a time now I’ve rolled back IPv6 on most my network to reduce the overhead of obscure troubleshooting problems with routers, streaming and device compatibility. From: AF < af-boun...@af.afmug.com > On Behalf Of Mike Hammett Sent: Monday, October 15, 2018 8:09 AM To: AnimalFarm Microwave Users Group < af@af.afmug.com > Subject: Re: [AFMUG] Tracking Down DualStack Problems Recursive server network location is a huge concern for CDNs. Nate is okay in this regard, but your recursive server *MUST* be on the network the request is coming from. ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP From: "Ken Hohhof" < af...@kwisp.com > To: "AnimalFarm Microwave Users Group" < af@af.afmug.com > Sent: Wednesday, October 10, 2018 12:04:30 PM Subject: Re: [AFMUG] Tracking Down DualStack Problems Authoritative DNS is under the control of the content provider, it shouldn't matter whose resolver you are using, unless the content provider is using something like anycast DNS which might infer from the IP address of the resolver which A and AAAA records you should see. As long as your DNS server can be correctly geolocated, then still it is the content provider's decision. BGP is a different matter, but for a big CDN, the decision will probably still be made based on where they have servers and who they peer with. If they have servers on Cogent and you are reachable via Cogent, it might not matter if BGP says that Telia would be a better route. But the post was about DNS. -----Original Message----- From: AF < af-boun...@af.afmug.com > On Behalf Of Nate Burke Sent: Wednesday, October 10, 2018 11:44 AM To: AnimalFarm Microwave Users Group < af@af.afmug.com > Subject: Re: [AFMUG] Tracking Down DualStack Problems I have my Own DNS servers, without a full time packet sniffer, how would you ever figure out what actual DNS lookup it did to find the host? Middle of the day, even a less optimal data center shouldn't be at capacity. The Wife said she was watching VUE on a different TV in the house Yesterday afternoon, and it was buffering as well. So It could be Vue and Their IP6 capacity. Still a pain to track down. On 10/10/2018 11:33 AM, Adam Moffett wrote: > I'm going to be pulling the trigger on dual stack pretty soon. You're > scaring me a little. > > I would think the major CDN's are dual stack by this point. I'm not > sure if it matters, but whose DNS were you using? It could be that > the v6 DNS took you to a less optimal data center than the v4 DNS. > > > On 10/10/2018 12:23 PM, Nate Burke wrote: >> I haven't rolled IPV6 out to customers yet, but I am running >> Dualstack at my house. Native IP6 with my own ARIN Space. I've >> noticed that streaming traffic, youtube, netflix, Playstation VUE, >> Facebook, seem to prefer the IP6 connection. This morning I was >> having all kinds of Buffering problems watching Playstation VUE, (Via >> Amazon FireTV box) I turned off IP6, it automatically switched to the >> IP4 stream, and is now flawless. Those of you running full Dualstack >> deployments, do you have to do IP4/6 troubleshooting? How do you >> manage troubleshooting with the customer to determine if the traffic >> stream is a 4 or 6, and track it down? From the customer >> perspective, "the internet sucks" because things are buffering. >> > > -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
