Name resolution broken? It was for me using IOS8 or OS X Yosemite to connect to a corporate Windows Server 2008 PPTP VPN. It worked fine before the upgrades using IOS7 and Mavericks, hostnames ending in .local resolved fine and remote desktop connection worked fine.
After googling, I began by thinking the problem was caused by the DHCP server missing option 119 (Domain Search List). I implemented this on the Windows Server 2008 DHCP but wasn’t convinced it was working as the UI requires the search domain to be encoded into ascii hex values with separators and null termination and the available docs found were contradictory.
However using dhcpdump, this showed the values coming back to the client but if it was working, the hostnames were still not resolving. If I manually added the search domains to Yosemite, the hostnames resolved ok, fine but not very elegant and also I couldn’t find a way to do this in IOS.
It seems Apple have become more strict with the .local suffix, so you need a SOA record set up in the domain name server. Pretty simple, add a new primary to your forward lookup, name it ‘local’ and that’s it.
My Apple devices using the VPN are now resolving hostnames on the corporate network.