Netflix advertises a lot of address space out via AS2906. Walking rDNS is easy, and from these two sources we can derive a list of names used by Netflix for content delivery. But we cannot necessarily spot Netflix edges co-located within ISPs.
The IPv4 space originating from AS2906 on 2017-04-18 totals 151,530 IPv4 addresses.
[WIP] A partial scan of about 93,000 IPv4 addresses surfaces 4,530 names.
These names are generally 7 levels deep (e.g., ipv4_1.cc1.c355.sjc002.dev.ix.nflxvideo.net.)
2201 names start with "ipv4", the single-stacked name that Netflix tends to use. For these, an "ipv6" (actually, dual-stacked) domain is likely to exist.
A more complete dataset was snarfed on 2017-06-21: https://gist.github.com/sdstrowes/2f010d19c7371dc3a4bd62953c216b3a
[WIP] In the set of surfaced names, there are 'dev' and 'ops' names.
[WIP] names so far appear to be names Netflix operates at an IXP (".ix.").
[WIP]
2 akl001
40 ams001
60 arn001
26 atl003
14 ber001
84 bos001
14 bru001
7 bue001
50 den001
166 dfw001
126 dfw003
22 dub001
20 dxb001
80 ewr002
10 gru003
1 gru004
59 gru005
20 hel001
20 hkg001
86 iad001
40 iah001
8 jnb001
20 las001
60 lax001
100 lax008
45 lhr001
30 lhr004
40 lhr005
38 mad001
31 mci001
30 mia005
34 mil001
42 msp001
90 nyc001
72 ord001
86 ord003
20 orf001
24 pdx001
40 phx001
5 phx002
6 pit001
16 poa001
12 rio001
20 san001
34 sea003
28 sin001
70 sjc002
36 sjc005
26 stl001
40 syd001
30 tyo001
14 vie001
14 waw001
14 zrh001
1064 cxl0
2 cxl1
824 lagg0
232 mce0
(FreeBSD network interface names and/or aggregated/bonded interfaces?)