9 ms·
Why does iTunes 10.7 try to contact the domain bogusapple.com?
- patio11 14y agoSounds like "A cheap way to figure out if we're in a restricted DNS environment like e.g. airport wifi pre-payment." The implementation is clearly suboptimal, though - you want to control the canary domain.
- bgrohman 14y agoSurely Apple wouldn't use a domain they don't control for this.
- alanh 14y agoIf you read the linked thread, it’s clear they did not, in fact, register or otherwise control the domain.
- bgrohman 14y agoRight. I should have been more clear in my statement. I meant that, since Apple clearly doesn't control the domain, I find it hard to believe that they would use it intentionally.
- niels_olson 14y agoMaybe it's a cheap way to drive up a squatter's bandwidth costs?
- VxJasonxV 14y agoI resent that.
- niels_olson 14y agoI was at work and the network had blocked it putting it in the "placeholders" category. Note to self: hacker news may be more reputable than the large government agency's IT management.
- derleth 14y ago> Note to self: hacker news may be more reputable than the large government agency's IT management. More clueful, certainly.
- VxJasonxV 14y agoI don't know exactly when it started, but I suspect Apple has used this domain for at least a few days now. Whether that's as far back as Mountain Lion's release, or as recently as iTunes 10.7. Considering some of our active theories, it may have only started becoming used as a result of that Terms & Conditions snafu that occurred the other day. Either way, the problem predates my registration of the domain, which was around 13 hours ago now. I registered bogusapple.com as a result of seeing use of the domain.
- avar 14y agoI think you're being overly generous in ascribing the intentions of an entire company on this. Most likely the real reason behind this is that some programmer in their employ who didn't know better hammered in "bogusapple.com" as the first thing he could come up with, committed it since it worked for him, and now a lot of people are trying to ascribe more complex intentions to Apple than that.
- bgrohman 14y agoCould be. I don't know much about the internal development practices at Apple. One has to assume they have strict development and testing guidelines, but you're right - it is possible that some programmer hammered this in, and the change slipped past the code review and testing phases.
- qeorge 14y agoWindows 7 does this in a cool way: http://superuser.com/a/277955 http://superuser.com/a/277955 It tries to load a text file over HTTP (http://www.msftncsi.com/ncsi.txt http://www.msftncsi.com/ncsi.txt) and fetch the DNS record of dns.msftncsi.com. If the return of either is not as expected, Windows indicates 'No Internet Access' (although you are connected to a network).
- __david__ 14y agoI think the "typo" scenario makes the most sense. bogus.apple.com vs bogusapple.com. It would be an easy mistake to make and everything would look like it's working fine until someone happened to register the domain.
- bking 14y agoThey just needed a placeholder to send it to and I would assume they would send it there to reduce any possible strain on their servers. Why not send it there is the question on my mind.
- corwinstephen 14y agoBecause they have no control over the content on that site. The owner could easily throw up some raunchy content, which would make for a weird experience when it comes to discussions like this one.
- reeses 14y agoOr, quite legitimately (I slay me), between RTM and pushing out the update, someone could have registered the domain and used it for content, then see their site hammered by irresponsible software publishers.
- ak217 14y agoThey should be using example.net. http://en.wikipedia.org/wiki/Example.com http://en.wikipedia.org/wiki/Example.com
- danielweber 14y agoIt depends what the purpose is. Maybe it's an anti-check on certain kinds of network connectivity. I can ping example.net and example.com.
- pronoiac 14y agobogus.apple.com came to mind first for me. I guess if an ISP resolved it, there might be cookie leakage.
- brey 14y agonope, example.com resolves just fine. apple's trying to test for non-existence. see .invalid - http://en.wikipedia.org/wiki/.invalid http://en.wikipedia.org/wiki/.invalid
- mtrimpe 14y agoYup; example.com is defined as not available for email not as far as DNS is concerned.
- mrng 14y agoChrome, too, does three initial lookups on start up to see if ISPs intercept requests that cannot be resolved. It compares the IP addresses of the pages that are returned, and turns the infobox off if they are identical (as this suggests an ISP is intercepting the look ups).
- secure 14y agoIt is worth pointing out that Chrome requests randomly generated nonsense, while bogusapple.com is always the same.
- mrng 14y agoAbsolutely right - I forgot to mention that in my initial comment. Chrome's behaviour makes much more sense than Apple's -- who hadn't even secured the bogusapple.com domains for themselves (as Microsoft did with Contoso, for example).
- ben1040 14y agoInteresting writeup about the Chrome behavior: https://isc.sans.edu/diary.html?storyid=10312 https://isc.sans.edu/diary.html?storyid=10312
- danielweber 14y agoI remember freaking out over those DNS lookups one day, wondering where the malware was. A coworker told me what was going on and so I could relax.
- jschuur 14y agoSame reason iOS connects to http://www.apple.com/library/test/success.html http://www.apple.com/library/test/success.html when you go on WiFi? Of course, the question then is, why don't they just use that one?
- TazeTSchnitzel 14y agoMicrosoft does something similar: http://technet.microsoft.com/en-us/library/cc766017%28WS.10%29.aspx http://technet.microsoft.com/en-us/library/cc766017%28WS.10%... They request http://www.msftncsi.com/ncsi.txt http://www.msftncsi.com/ncsi.txt and check the DNS of msftncsi.com
- its_so_on 14y ago#creative (see [1]) The Apple implementation is "logically the same" as the Microsoft implementation, yet so much cleaner. check for yourself. http://www.apple.com/library/test/success.html http://www.apple.com/library/test/success.html vs http://www.msftncsi.com/ncsi.txt http://www.msftncsi.com/ncsi.txt i won't comment on the differences, which include the meaningless URL and useless "ncsi" in the text, and the fact that it still looks like an error rather than a successful test page. The Apple page is absolutely minimal. Yet everything is in its place, and it can't leave any developer confused for a millisecond, or make a typo, as it's a human English word at a human, English URL. Apple is Apple. Microsoft is a split millisecond of headache for a developer who rechecks his spelling of "ncsi" and the whole meaning of the ncsi concept three times to make sure his code is correct. just like windows versus mac. yeah, it's logically the same. but one just works, one requires a three-page document. http://technet.microsoft.com/en-us/library/cc766017%28WS.10%29.aspx http://technet.microsoft.com/en-us/library/cc766017%28WS.10%... ---- [1] This post is tagged as being creative (as opposed to rational). as a note, about half of my posts speak to creativity and design and half speak to rationality and logic. most people only do one or the other, so i can understand why each group is confused by the other. this lets me build two brands. just ignore the posts that don't apply to you.
- TazeTSchnitzel 14y ago
- bitcartel 14y agoThis reminds me of the recent iOS 6 wifi connection problem, where a web page on the Apple site was broken or removed accidentally, causing wifi to be disabled. http://arstechnica.com/apple/2012/09/wifi-connectivity-under-ios-6-temporarily-broken-by-server-proble/ http://arstechnica.com/apple/2012/09/wifi-connectivity-under... Now, it's the reverse situation. If iTunes and the App Store expect bogusapple.com to not resolve, what happens when it does? Why did Apple not own this domain?
- VxJasonxV 14y agoI was very concerned that this could occur when I picked up the domain and started allowed traffic to it to succeed, but I haven't seen the massive social network outcry about problems... So I've put that concern to rest :). As said elsewhere, I think the theory that they likely intended 'bogus.apple.com' is the best guess. Either way it was just a consideration that some developer and/or their code reviewer(s) overlooked. It happens.
- cyber 14y agoOddly, I keep getting requests from people trying to buy my "DNS configured, but no web site" domain I use for testing. (Right now DNSSIG is expired, and if one examines the rest of the headers, it's obvious it was configured expired.)
- VonGuard 14y agoIs this a subtle way of DDoS'ing a site they don't like?
- tamersalama 14y agoAfter the domain was registered (and assuming no change in iTunes & App Store) - I'm curious to know who owns the right to the domain. And possibility of domain sale.
- wilfra 14y agoApple would have no problem taking this away if they filed a WIPO claim. He clearly registered it in 'bad faith' (a legal term) and is willfully and purposely violating their trademark. I suspect though all they would have to do is ask and he'd hand it over - perhaps with a letter threatening legal action if he didn't immediately comply.
- VxJasonxV 14y agoAssuming that they don't just fix the problem (see my first-level comment), I do hope any response I see from them is tactful.
- pbhjpbhj 14y ago>is willfully and purposely violating their trademark.// Go on. He's not trading using the Apple Computers trademark nor is their any confusion. There is nothing clear about his intention, there is no mens rea nor actus rea that can be established from the information in this thread AFAICT. Apple have no automatic right to everything bearing the name "Apple". They have no more right to the bogusapple.com domain than they have a right to a box of [fruit] apples from your local grocer. Will they get the domain if they wish it? Are mega-corps in control of the law in the USA? WIPO - they've erred before and will do so again I feel; they appear to have a presumption that the world belongs to corporations and don't have an interest in protecting the rights of citizens. Not unlike some governments it seems.
- wilfra 14y agoThe Apple in this domain refers to the trademarked Apple. He doesn't even attempt to hide that on the page, referring directly to the company himself. That is where the proof for willful trademark infringement comes from. If he had owned this domain for years and it was a blog about his favorite fruit, then he'd have a strong case to keep it. Given the way he's using it I doubt Apple would ever do anything more than ask him for the domain. But if he were to do something like put up a porn site or even run ads, they might be pissed off enough to sue him for the domain + damages - and they'd likely win.
- DigitalSea 14y agoPretty sloppy on Apple's end if you ask me. Why check for a domain that you don't actually own? Imagine if someone bought the domain and worked out how to maliciously use it to their advantage? (I seriously doubt that's possible though). What kind of info was being sent to this domain, was it just a standard request to see if there is connectivity or was other information sent that could be used to identify a user? Sounds sub-par just like how the Wifi functionality does a request to: http://www.apple.com/library/test/success.html http://www.apple.com/library/test/success.html
- deleted 14y ago[deleted]
- VxJasonxV 14y agoA lot of folks are suggesting it was a typo, and they intended to use bogus.apple.com instead, which is very very likely. I can tell you with 100% certainty that standard HTTP request information is being sent to the domain. So, IPs for the connection, User Agents of the software used to connect, and the request URL. That's pretty much it in a nutshell. I've seen a few iTunes UAs, both Windows and Mac, and since this news has made the rounds, the signal to noise ratio just went wayyyyyy down. (Go figure.)
- MichaelApproved 14y agoIt's still a sloppy name: "Bogus" ? Why not something more descriptive and less suspicious like netcheck.apple.com
- pavlominus 14y agoClearly a bug that got through QA. What a mess Apple is becoming.
- VxJasonxV 14y agoAll of this grief over what may amount to missing a single dot? (bogus.apple.com) STEVE JOBS IS ROLLING IN HIS GRAVE OVER THIS GOD AWFUL FAILURE ON TIM COOK'S PART!
- pavlominus 14y agoAgreed. Some developer didn't go back to fix it. Heads are gonna roll.
- skeletonjelly 14y agoYou jest, and we have the benefit of hindsight, but you can't use the "just a single dot" defense when Apple themselves tout their attention to detail with every product release (wasn't there something about their product design team now working on a nano/micrometer scale?)
- VxJasonxV 14y agoHi everyone. I registered bogusapple.com after a buddy of mine posted a screenshot of Little Snitch prompting iTunes' access to the domain. All credit for finding this snafu goes to gentmatt, and my bank account for allowing me the ability to frivolously buy a domain. I don't believe that accessing this domain is built directly into the compiled code of apps, since (in my opinion) it did not happen close enough to a software update. I believe it is just some kind of a typo (bogus.apple.com?) for something used as part of the web page views that comprise the iTunes and the Mac App Store apps. I fully expect that this problem will quietly go away once they deploy new versions. I picked up the domain just to see if any particularly exciting web requests were being made, and it's been fun to watch user agents, but as soon as Twitter, news sites, and forums got wind of it, it's pretty much impossible for me to discern any meaningful traffic anymore. I suppose I could start filtering any requests with a referer, or ones not coming from *.apple.com. We'll see. It's been a fun 13 hours. Any questions?
- avar 14y agoNot a question but just a word of advice to be careful. What you did could to a layperson be construed as intentionally exploiting a bug in their software with the result that you're now intercepting requests from unsuspecting customers of theirs, and getting data via your logs that in some countries falls under privacy laws. Depending on how big of an embarrassment this turns out to be for them and how well funded their legal department is this might not turn out to be hassle-free for you.
- famousactress 14y agoThat's a shame, since the first thing that occurred to me was thank goodness someone with nefarious intentions didn't buy the domain and attempt to pass it off as something Apple owned (and thereby users might trust).
- stcredzero 14y agoHe should get permission to host a bunch of #fakestevejobs content. (Parodic tribute stuff, of course.)
- brey 14y agoif they want to test for domain non-existence, that's what the .invalid TLD is good for. http://en.wikipedia.org/wiki/.invalid http://en.wikipedia.org/wiki/.invalid
- benjoffe 14y agoI wonder, do any routers, proxies or local internet exchanges filter requests based on TLDs that don't exist in a dictionary of valid TLDs? I'm guessing at least some do, which may give incorrect results.
- keikun17 14y agoa development/test code that got into the build?
- VxJasonxV 14y agoIt looks like this was never a connectivity test, but some sort of outright statistics hostname error: https://discussions.apple.com/message/19852289#19852289 https://discussions.apple.com/message/19852289#19852289 And it looks like the issue's already been fixed too (two posts down).
- VxJasonxV 14y agoAs best as we can tell, this issue started in the late evening Sunday, registration occurred very early in the morning Monday, and was subsequently resolved later in the day: https://discussions.apple.com/message/19852289#19852289 https://discussions.apple.com/message/19852289#19852289 And it appears it was never about DNS resolution / network discoverability.
- VxJasonxV 14y agoIt appears this was never for network discoverability, but stats instead, and a bad hostname was simply filled in: https://discussions.apple.com/message/19852289#19852289 https://discussions.apple.com/message/19852289#19852289 Perhaps for testing purposes? "What happens when the stats server isn't reachable?" And then it got left that way, WHOOPS. Long story short, this problem appears to have been resolved the same day it started, since it did not require a software update to fix, they just updated the web views for their store pages. Is anyone still concretely still seeing the problem?