<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"  xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">
	<channel>
		<title>TidBITS: Comments on Solving the App Store’s NSURLErrorDomain Error</title>
		<link>http://tidbits.com/</link>
		<description>After finding himself unable to get updates via the App Store app, Adam Engst changed his DNS servers and everything suddenly started working.</description>
		<language>en-us</language>
		<copyright>Copyright 2012 TidBITS Publishing Inc.</copyright>
		<pubDate>Tue, 02 Oct 2012 00:00:00 EDT</pubDate>
		<lastBuildDate>Tue, 02 Oct 2012 00:00:00 EDT</lastBuildDate>
		<managingEditor>editors@tidbits.com (TidBITS Editors)</managingEditor>
		<webMaster>editors@tidbits.com (TidBITS Editors)</webMaster>
		<creativeCommons:license><![CDATA[http://tidbits.com/terms/]]></creativeCommons:license>
		<image>
			<title>TidBITS</title> 
			<url>http://tidbits.com/images/tb_logo_152x55.png</url> 
			<link>http://tidbits.com/</link> 
			<height>55</height>
			<width>152</width>
			<description>TidBITS badge</description> 
		</image>
		
		<item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15909</link>
			<pubDate>Tue, 02 Oct 2012 11:05:56 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15909</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[A technical friend commented in email:<br><br>You want this Terminal command instead:<br><br>        sudo dscacheutil -flushcache<br><br>mDNSResponder doesn’t control the regular DNS cache (unless something changed recently).]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15752</link>
			<pubDate>Thu, 20 Sep 2012 13:45:51 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15752</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Could be! I've seen that fix for iOS device errors with the App Store app, where you might not even be able to mess with DNS. In this situation, the Mac App Store itself seemed available; just not updates.]]></description>
		</item><item>
			<title><![CDATA[Comment from Matt Neuburg]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15751</link>
			<pubDate>Thu, 20 Sep 2012 13:41:40 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15751</guid>
			<author><![CDATA[comments@tidbits.com (Matt Neuburg)]]></author>
			<description><![CDATA[But I had what sounds like the same problem with my Mom's iPad (it couldn't see the App Store) and solved it by having her artificially set the date to several years in the future, try to connect to the App Store, then set the date back to the real date and time. After that, everything worked fine. I'm wondering if there was a certificate issue, and playing with the date threw out the cached certificate, or something.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15665</link>
			<pubDate>Mon, 17 Sep 2012 08:39:44 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15665</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Seems a little unlikely that this is an OpenDNS bug, since others have reported the problem who aren't using OpenDNS. It may be a bug in DNS software that is used by multiple DNS servers, but that's a different issue.]]></description>
		</item><item>
			<title><![CDATA[Comment from Mitch Strickland]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15658</link>
			<pubDate>Sat, 15 Sep 2012 04:28:53 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15658</guid>
			<author><![CDATA[comments@tidbits.com (Mitch Strickland)]]></author>
			<description><![CDATA[I was experiencing the same problem using one of Earthlink's opt-out server for primary DNS (207.69.188.172). I was able to solve the problem by promoting my secondary DNS server (Google DNS) to primary.]]></description>
		</item><item>
			<title><![CDATA[Comment from Curtis Wilcox]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15651</link>
			<pubDate>Fri, 14 Sep 2012 12:15:44 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15651</guid>
			<author><![CDATA[comments@tidbits.com (Curtis Wilcox)]]></author>
			<description><![CDATA[The App Store progress bar said the iTunes 10.7 update on my otherwise fully updated OS X 10.8.1 system was 163.3MB. If you download it from the web site, it's 157.33MB. The previous downloadable, iTunes 10.6.3, is bigger, 170.27MB, which makes sense since 10.7 is the first Intel-only version of iTunes.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15648</link>
			<pubDate>Fri, 14 Sep 2012 07:51:54 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15648</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[I don't think the App Store app shows the size before you download, but if you have automatic downloads turned off, I think you can see a progress bar that includes the size after you click the Update button. All guesswork at the moment, since automatic downloads was turned on for all my Macs, so I won't know for sure until a new update arrives.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15647</link>
			<pubDate>Fri, 14 Sep 2012 07:45:26 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15647</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Fascinating - that would indicate more of a local problem that would be in Apple's purview rather than anything related to which servers were in use. Switching servers would very likely cause the DNS cache to be flushed as well.]]></description>
		</item><item>
			<title><![CDATA[Comment from Curtis Wilcox]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15644</link>
			<pubDate>Fri, 14 Sep 2012 04:48:30 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15644</guid>
			<author><![CDATA[comments@tidbits.com (Curtis Wilcox)]]></author>
			<description><![CDATA[Whatever the cause of this App Store error, it's not limited to OpenDNS. I experienced it with a computer yesterday on a university network and using the university's DNS servers. The university uses Infoblox to manage DNS.]]></description>
		</item><item>
			<title><![CDATA[Comment from Glenn Fleishman]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15643</link>
			<pubDate>Thu, 13 Sep 2012 23:48:20 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15643</guid>
			<author><![CDATA[comments@tidbits.com (Glenn Fleishman)]]></author>
			<description><![CDATA[Bill, that's a little strident. OpenDNS is an optional service that people choose to use and can stop using with a tiny change.]]></description>
		</item><item>
			<title><![CDATA[Comment from Bill Cole]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15642</link>
			<pubDate>Thu, 13 Sep 2012 23:24:18 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15642</guid>
			<author><![CDATA[comments@tidbits.com (Bill Cole)]]></author>
			<description><![CDATA[The answer is definitely that OpenDNS has a bug, and it may well be precisely in the Flashback blocking done by OpenDNS. That error code indicates a missing file *ON AN HTTP SERVER* (i.e. a "404" HTTP reply) and that would be what you'd expect from using a DNS server that tells you lies for your own good about what it deems to be bad domains. If OpenDNS has misidentified the Apple update machines as carrying bad stuff (maybe because they *DO* serve out files with malware patterns) they will give you bogus addresses for their names. If they are pointing the "bad" names at machines with empty web servers on them, you get a fast 404 to nearly any request. Anything using Core Foundation Networking will turn that into a -1100. <br>This is an demo of the risk of "white lie" DNS as a tool for protecting people from bad stuff.]]></description>
		</item><item>
			<title><![CDATA[Comment from Mike Polinske]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15641</link>
			<pubDate>Thu, 13 Sep 2012 20:56:34 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15641</guid>
			<author><![CDATA[comments@tidbits.com (Mike Polinske)]]></author>
			<description><![CDATA[I flushed the DNS cache after seeing the suggestion on the Apple Discussion forum and that worked.  In Terminal, enter the following:<br><br>sudo killall -HUP mDNSResponder<br><br>Here is the link https://discussions.apple.com/thread/4289718?start=0&tstart=0]]></description>
		</item><item>
			<title><![CDATA[Comment from Karl Warschau]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15640</link>
			<pubDate>Thu, 13 Sep 2012 18:54:54 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15640</guid>
			<author><![CDATA[comments@tidbits.com (Karl Warschau)]]></author>
			<description><![CDATA[Thanks for asking David. I was literally just asking myself the same question. Anyone know?]]></description>
		</item><item>
			<title><![CDATA[Comment from jdh]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15639</link>
			<pubDate>Thu, 13 Sep 2012 18:45:44 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15639</guid>
			<author><![CDATA[comments@tidbits.com (jdh)]]></author>
			<description><![CDATA[I'm using OpenDNS and had the error last night, but it has since resolved, at least for me. I downloaded the iTunes update with no trouble tonight.<br><br>I did not change DNS servers.]]></description>
		</item><item>
			<title><![CDATA[Comment from David Nuss]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15637</link>
			<pubDate>Thu, 13 Sep 2012 17:01:46 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15637</guid>
			<author><![CDATA[comments@tidbits.com (David Nuss)]]></author>
			<description><![CDATA[Slightly off-topic but related to app store updates... Anyone know why they don't show the size of the update, as they do in iTunes with iOS apps? Or if there is a setting I can change? Or just complain to Apple?]]></description>
		</item><item>
			<title><![CDATA[Comment from Glenn Fleishman]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15636</link>
			<pubDate>Thu, 13 Sep 2012 16:49:15 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15636</guid>
			<author><![CDATA[comments@tidbits.com (Glenn Fleishman)]]></author>
			<description><![CDATA[I may have an answer. OpenDNS can have issues with content-distribution networks (CDNs) that rely on cues from an IP address requesting a DNS lookup to provide a "nearby" (in terms of Internet hops) content server.<br><br>I've seen this with Apple when I use OpenDNS and try to download something from the developer site or other places. It often crawls. If I switch DNS servers to Comcast's, it speeds up.<br><br>Google uses slightly different cues, and it seems that it might be better telling a CDN where the user is. I'm surprised to see an actual error, but this does sound similar.<br><br>There's a proposal in the words to update DNS servers (and only major ones would have to adopt the patch) so that a public DNS provider could give a little information about the source of a DNS request to help nudge the CDN to offer a server that's correctly close enough.]]></description>
		</item><item>
			<title><![CDATA[Comment from Mitch Kearns]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15635</link>
			<pubDate>Thu, 13 Sep 2012 16:49:14 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15635</guid>
			<author><![CDATA[comments@tidbits.com (Mitch Kearns)]]></author>
			<description><![CDATA[I had this error too, tried this change & it worked. Probably a flush DNS problem. Thanks for the help.]]></description>
		</item><item>
			<title><![CDATA[Comment from Michael E. Cohen]]></title>
			<link>http://db.tidbits.com/article/13259?rss#comments_15634</link>
			<pubDate>Thu, 13 Sep 2012 16:48:22 EDT</pubDate>
			<guid>http://tidbits.com/article/13259#comments_15634</guid>
			<author><![CDATA[comments@tidbits.com (Michael E. Cohen)]]></author>
			<description><![CDATA[In my case, I saw the update in Software Update and was able to download and install it, following which I got the message. Freakier!]]></description>
		</item>	
		
	</channel>
</rss>