cannot access .local domain/intranet site when connected to the VPN after the IOS 8 update.

I had the same problem, after upgrading to osx yosemite my macbook could no longer access .local domains over the VPN. The solution was to both:

• Add the "local" forward lookup zone to the windows DNS server
• Add the "local" search domain to the DNS options (Advanced > DNS)

Add the local zone to MS DNS worked for me. Simply adding the search domain in OS X VPN settings did not. Thanks!

Not able to browse intranet sites when i am conected over corporate wifi which was working all fine till iOS8 upgrade. Forget the VPN etc also (which definitely doesn't work).

Sincerely this is epic fail. One of the reasons I wasn't upgrading to iOS8.0.2 from iOS7 is to see such kind of bugs.This wasn't mentioned anywhere in release notes as a /feature/. These are some of the time waste things you land up which are not acceptable really in corporate usage for any product.. Phew!

Anybody has a workaround for this ?

Until iOS 7 everything worked fine with our .local domains, with 8.0.2 I needed to add a SOA entry for the x.y.local domain.

Now with 8.1 I again needed to change the DNS server config: I had to add a SOA for local. and for y.local. in addition to the already existing SOA for x.y.local.

What annoys me the most is that there is no official response. Nothing. Bug reports are closed "as duplicate of bug 123". But you are not allowed to see bug 123..

Seriously, this is a slap in the face of every network admin dealing with iOS devices. Apple, do you really NOT care at all for corporate / business usage of your products?

I am still facing the problem even after updating to IOS 8.1.1. I can't download mails from exchange server (SBS 2008) when I am connected to server via VPN. Establishing VPN connection is no problem. Downloading mails from exchange server when I am in same network as exchange server is no problem either.

I hoped Apple would fix this with IOS 8.1.1 but seems not to be fixed.

W T F. I just updated to 8.1.1 and noticed that it again does not work anymore.

So with iOS 7, everything worked fine. Then with iOS 8.0.2 we needed the SOA record for the xx.yy.local domain, then with iOS 8.1 I needed to add a SOA for local alone, and now with iOS 8.1.1 it does not work even with all SOA records set...

Apple, do you care at all about bugs in your software?

How is no one understanding Apple's logic here...???

It's obvious by now that the inability to resolve local domains via VPN in iOS 8 was in fact a feature that Apple deliberately added. The SOA record workaround which although fixed the problem for us, was interpreted as a bug in the VPN feature by Apple, which Apple resolved by making the SOA record no longer work.

Apple clearly do not care; they do not post ANY feedback to their forums and apparently the bug reports that everyone posts are "duplicates", yet as each release happens, the problem is NEVER mentioned as a "known issue" in their release notes. The latest 8.1.1 release notes do not mention any known issues with DNS or VPN.

Don't bother trying to convince Apple this issue is an issue which needs resolving. It's not an issue to Apple and does not affect their ability to do business or make money. They've had plenty of opportunity to do so since iOS 8 was released. This feature is here to stay.

How should this be a feature? I am not even using a VPN, I am using internal .local DNS zones to point to some IP addresses in my LAN.

What's the gain here for Apple to add this "feature" if you can see through Apple's logic so clearly?

Sorry, I assumed you had a sense of humour and would detect the sarcasm in my post.

I spoke to Apple this morning and I'm scheduled to have a call back from phone support. However, I asked why no one from Apple has responded to this thread, and was told:

"We do have Apple techs that do watch the discussions. I cannot say why this particular issue has not been addressed. You are honestly the first person that I have assisted that has had this issue, not saying that no one else has contacted with this issue. That is why I would like to get it escalated to make sure it is addressed."

The same tech has advised me that someone from Apple will finally be posting an acknowledgement shortly and hopefully will provide more details on the status of their investigation into this issue.

I considered the possibility for a moment. ^^

"No one else has contacted us with this issue" is also a good example of sarcasm.

For any Apple representative reading this, I filed this bug with the Radar ID #

18478304, which was later closed as a duplicate of bug #17410938

And thanks to the great Apple Radar I of course cannot see bug #17410938.

Can I add myself to the list of unsatisfied users who naively upgraded XCode to v6.1, and now I can't get the iOS Simulator (v7.1 or v8.1) to connect to my company's intranet anymore.

My iPad and MacBook (which XCode and the Simulator is running on) are both connected to the same internal WiFi network.

The iPad & MacBook's copy of Safari can both happily call the JSON web services on our intranet, but the Simulator just throws a "A server with the specified hostname could not be found." error. This happens on in my iPad app, and if I go onto Safari on the Simulator and try the same internal URL there.

I did try adding "local" to my MacBook's DNS settings... but it made no difference.

Prior to upgrading XCode/Simulator, it all worked fine.

http://stackoverflow.com/questions/26992605/ios-simulator-8-1-cant-connect-to-in tranet

Has anyone heard from Apple yet, or are they all on a beach, counting their money...?

IOS 8.1 and 8.1.1 connected via 3G over private APN (connecting to our DNS servers) I have the same problem.

Any DNS query to server.us.local doens't even get sent to the DNS server.
All other queries get sent.

A fix would be good..

I recently attempted to get some assistance through chat support. Unfortunately, they stated the issue is with the remote desktop client apps and I need to contact their developers. Is the fault with Microsoft's RD client app or Apple's OS?

Apple are talking crap. And the fact they haven't bothered to reply to this post to reassure their loyal customers they are aware and doing something about the issue suggests they don't really care. As long as we are paying them, lining their pockets, that's all that matters.

Apparently Apple have "tech" people that scan these forums for issues like this and respond accordingly, or at least that's what they told me the last time I contacted them via chat, about a fortnight ago! What a load of crap!