-
All replies
-
Helpful answers
-
Oct 17, 2014 10:36 PM in response to davidencoby Akademuk,Same problem in Yosemite! Apple, what'a f#$k?
-
Oct 17, 2014 10:41 PM in response to Akademukby adrenaln,What version of windows DNS are you running? Is there a delegation from local to domain.local in the local zone?
-
Oct 17, 2014 10:51 PM in response to adrenalnby Akademuk,Windows 2012, but why i must create local zone? Why? It's not necessary for my corporate network.
-
Oct 17, 2014 11:06 PM in response to Akademukby adrenaln,Im only speculating here, but I'd imagine that it is to ensure correct DNS behaiviour as per the standard and reduce the load on root name servers from incorrectly configured Vpns and private networks
-
Oct 19, 2014 8:53 AM in response to adrenalnby Akademuk,I hope we have found decision - VPN (dhcp) server must announce option-119 to all clients. Option-119 is a domain search list which must include yours domain.local zones. I can verify my investigation only tomorrow.
P.S. Manual setup "domain search" list on VPN-connection resolved problem on my macbook air (yosemite 10.10).
-
Oct 19, 2014 1:57 PM in response to Akademukby davidenco,You cannot change network settings on a VPN connection in iOS 8.
I have tried adding DHCP option 119 to our Windows DNS server and connecting the VPN on my iPhone but to no avail.
Still think Apple need to pull their finger out and fix this problem.
-
Oct 19, 2014 9:30 PM in response to davidencoby Akademuk,Where am i wrote about changing settings in ios8? Try to announce option 15 - domain name.
-
Oct 20, 2014 12:38 AM in response to Akademukby davidenco,This thread is related to iOS 8.
Option 15 is enabled by default in Windows DNS and has no effect.
-
Oct 20, 2014 1:38 AM in response to davidencoby Akademuk,We solved problem by using Cisco IPSec with domain name option.
-
Oct 20, 2014 3:42 AM in response to Akademukby clemensg,Apple closed my Radar bug report with "Duplicate of ...".
So it is definitely a known problem but who knows if they fix it any time soon. Since I serve the SOA record I don't have any more problems but it sure is a useless change, bothering many network admins around the globe.
-
-
Oct 23, 2014 8:39 AM in response to d3nnis.cby cathantric,+1 for local zone fix does not work
We're on AD 2008, created Forward Looking Zone called "local", SOA exists, clients (iPad and iPhone) still unable to resolve FQDN with domain.local
-
Oct 23, 2014 8:57 AM in response to duanelby duanel,Updated: This did not work. Even though I restarted after making this change and clearing out my /etc/hosts file, something must have been cached. This stopped working for me this morning:
There was a similar issue in 2002 with OS X. I found a few articles about it and I've been able to address this issue by simply adding "local" to the Search Domains in the advanced network properties of my network interface. This has allowed those of connecting via VPN to resolve.
-
-
Oct 28, 2014 9:17 AM in response to oktssby davidenco,Yes, it doesn't work.
It's nice that Apple have taken an interest...

