Obi-wan_Kenobi
asked on
.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.loc al
Is there a way that I can rewrite these DNS requests for "sharepoint" to be "sharepoint.companyname.lo cal"? 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.
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.loc
Is there a way that I can rewrite these DNS requests for "sharepoint" to be "sharepoint.companyname.lo
I would prefer to stay away from any type of javascript redirect on our IIS servers to rewrite the request properly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tried adding a cname (testcname.companyname.loc al) 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*
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*
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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 ...
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 ...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.