I am unable to download ios 8 software update into my iphone. Anyone else having problems? Apple thinks it s a fios problem. Help!
Apple is actually having trouble with a handful of their CDN's going into a black hole.
There are different fixes that work for different geographic locations,
Using Google DNS is the one that I am seeing works most often, and the others are rather advanced fixes or work arounds.
If the following fix doesn't work then try to download it from work or a friend or neighbors house.
On iOS: Settings > WiFi > tap on the "i" icon next to your current network > Tap in the DNS box and change the address. to 8.8.4.4 and also 8.8.8.8
*Edit, new updated DNS that may work if the previous ones did not.
Great advice. Google DNS server did not work for me. Used the following link:http://pcsupport.about.com/od/tipstricks/a/free-public-dns-servers.htmChose Level3 DNS (209.244.0.3). Downloaded in minutes (instead of hours)
I'm sorry we pay a lot of money to be able to download it from our houses. Verizon needs to acknowledge this and fix it. It has been going on now for at least 6 days.
Apple owns those CDN's, and you pay handsomely to Apple as well. They can fix it with a few mouse clicks because they control how they send you a download, meaning what network path it takes.
When you change DNS then Apple's servers think you are somewhere else and they send it to you via a different path.
Verizon doesn't dictate that path, and can't control what path Apple is sending you data from.
The other fixes involve you getting a VPN that once again tricks apple into thinking you are somewhere else, and then they change the CDN that delivers your download.
The more advanced step is to completely block the bad apple CDN's and then apple can't use them, and they default to another CDN
Verizon is one side of the peering connection, are they not? They have the power to resolve this issue. As their customer I should not have to be in the middle of a peering issue. Sure I can fix this in many ways, but I shouldn't have to waste my personal time doing so that's what I pay them for.
Please fix this widespread problem ASAP.
FWIW Apple literally just Built this CDN. They did put a lot of money into it, but they are new comers to Owning and Operating their OWN CDN and there might be some learning curves, especially for their front line employee's.
They used to farm this out to industry leaders Level 3 and Akamai who still handle their ITUNES updates, but this was their big foray into the CDN world.
@Hubrisnxs wrote:Fwiw I'm just sharing what I see as the most common fix for people that aren't interested in making giants move but just want their updates.
I appreciate that you are helping, as I am sure the people you are helping appreciate it as well.
In my opinion they shouldn't even have to know this stuff or make any changes for these two companies to work together. As I am sure some just want a resolution even if they have to work around the issue themselves. But the end result may be that the issue is not resolved and continue into unforeseen future.
hclyatt. I went to my friend's house to use his TWC to upgrade my iPhone. It took 20 min vs. 23hours on FIOS (even after changing the DNS - nothing has helped). I upgraded my iPad at work (also around 20min). I simply gave up. It's almost a week after iOS8 release and Verizon is not willing to resolve the (peering?) issue. No more comments...
@mejdzer wrote: @hclyatt. I went to my friend's house to use his TWC to upgrade my iPhone. It took 20 min vs. 23hours on FIOS (even after changing the DNS - nothing has helped). I upgraded my iPad at work (also around 20min). I simply gave up. It's almost a week after iOS8 release and Verizon is not willing to resolve the (peering?) issue. No more comments...
@hclyatt. I went to my friend's house to use his TWC to upgrade my iPhone. It took 20 min vs. 23hours on FIOS (even after changing the DNS - nothing has helped). I upgraded my iPad at work (also around 20min). I simply gave up. It's almost a week after iOS8 release and Verizon is not willing to resolve the (peering?) issue. No more comments...
There were three work arounds for Apple's CDN in your area. The one that worked the most is the DNS, but there was also a VPN and for the instances where the DNS change fails called Null Routing.
When you change DNS, you're just redirected to another alpha quality Apple CDN node, in your cased, it was also broken. That is why the null routing idea makes sense, it will cause you to fail back to Akamai, an industry leading CDN who has experience delivering big software updates at blazing speeds.You can do this on most home routers also by placing a static route (in Advanced Settings) to 17.253.0.0/16, with a next-hop of 127.0.0.1.Try it, you won't be disappointed.
At first I was skeptical about the benifit of using an alternitive DNS server until I noticed that the Google DNS produced different IP addresses for the CDN then the Verizon (FIOS) DNS server. Since I had had a lot of experience managing Internet routing, here is what I think has been happening. The alternative DNS will access a lesser used CDN then that which the FIOS DNS finds and thus because the other may have a lower load, it will perform better.
Using the Google DNS (8.8.8.8) I was able to download IOS 8 for my iPad in about an hour as opposed to the 20 or more hours via the FIOS DNS. However as someone else has said, the alternative address will not allways give a better result, it depends on chance.