.local Domain issues on iOS 4.3 iPad

After updating to iOS 4.3 our users are unable to access internal addresses solely by the machine name.  FYI our TLD is companyname.local.

For example, they were once able to browse to http://sharepoint but now have to use the FQDN to access the site (http://sharepoint.companyname.local)  This is true for any resource on our internal network.

I did a couple packet captures on our DNS server (Windows Server 2003 R2) and found that any iPad on iOS 4.3 is dropping the domain suffix companyname.local.  iPads running iOS 4.2 query the DNS server correctly as it comes across as sharepoint.companyname.local

Is there a way that I can rewrite these DNS requests for "sharepoint" to be "sharepoint.companyname.local"? This traffic never hits our firewall so I'm unable to do any type of DNS doctoring.

 I would prefer to stay away from any type of javascript redirect on our IIS servers to rewrite the request properly.  


Obi-wan_KenobiAsked:
Who is Participating?
 
Glen KnightCommented:
Are  you specifying a DNS suffix in your DHCP? If you check under Settings > Wifi > wireless_network_name > Search Domains, does your internal Domain name appear here?
if not, you need to add option 015 DNS Domain Name to your DHCP Scope Options.
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
This is because you most likely do not have C Name records set up.

If you want to reach servers or website by their computer name, you have to set these up in DNS.
0
 
Obi-wan_KenobiAuthor Commented:
demazter - Yes, our DHCP is handing out option 15 for companyname.local.  On the iPads companyname.local shows up under "Search Domains" in the network configuration.

nappy_d - I was under the impression that it was best to use A/AAAA records and to avoid cnames because they require 2 lookups but I will still try and add a record for one of our resources and report back!

Thanks.

0
WEBINAR: 10 Easy Ways to Lose a Password

Join us on June 27th at 8 am PDT to learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees. We'll cover the importance of multi-factor authentication and how these solutions can better protect your business!

 
Obi-wan_KenobiAuthor Commented:
Tried adding a cname (testcname.companyname.local) for one of our apache servers then fired up Wireshark on our DNS server.

Using an iPad on iOS 4.2 the test cname record works fine.

Using an iPad on iOS 4.3 I'm seeing the same behavior as before, it's dropping companyname.local before the query even gets to the DNS server.

*boggle*



0
 
earthsoundCommented:
It's a bug, from what I understand. I can think of three workarounds you could try:

1) set a Search Domain in your wifi network(s) settings of companyname.local (which it appears you've tried).
2) edit /etc/hosts (requires root)
3) use a proxy server
0
 
GugroCommented:
Yes it seems to be a bug. There is a discussion on Apple's site too:
https://discussions.apple.com/message/15014573#15014573

We have the same problem here and I contacted the Apple support, but they told me, that they will charge 150,- € , as this is not an "normal user" issue, but I have to contact a special "company" support center ...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.