iPhone useless on a .local domain

You can send feedback - http://apple.com/feedback

The iPhone can't connect to other devices within a network if I understand what you are trying to do.

The directions in the knowledge base article are for Mac computers running OS X (10.3 & 10.4). The iPhone does not have the ability to configure .local domains at this time.

I wasn't able to find much information on this beyond another forum where someone said they put local in the field with no dot.

"Domain" is such a overused term ( read: Thanks a lot Microsoft ).

A "search domain" ( term is most commonly used in Unix, Linux and thusly OS X ) is a name appened to a non absolute DNS name if that name cannot be resolved into an IP address by the configured DNS server. A non absolute DNS name is any DNS name not ending in a period. Therefore "domaincontroller" is not the same as "domaincontroller."

for example:
1) Lets say you have a server with a configured DNS name of server.mycompany.local -and- a correctly configured internal/private DNS server.

2) You've set your "search domain" to "mycompany.local" on your workstation.

3) On your workstation, you try to lookup the name "server" which will initially fail. Before the workstaiton gives up on resolving the name it will add "mycompany.local" to the end of "server" giving "server.mycompany.local" wich will then succeed in returning an IP address.

now, A few things for you to check:

1) what DNS server is the iPhone set to use? is it a public or an ISP DNS server? ( which will fail to resolve anything in .local ) -or- is it an internal DNS server? ( which, if correctly configured, should append .local to any name an resolve it if that name exists on your private DNS server )

2) It sounds like you're dealing with an AD Domain ".local" is not enough to describe the full path to an AD Domain. Its going to be something like "netboisname.local" if so, that should be your "search domain."

I would guess that, most likely, your problem is that you've configured ( or DHCP has ) the DNS server as an ISP or some other public server which has no knowledge of anything in .local.

You're iPhone needs to use the same DNS server that your domain controller uses to enter the AD SVR records.

Who wonderful. Microsoft's entire reccomendation for internal domain naming involves using '.local' on the end. Here I have spent 400 bucks on a Iphone 3G to use remotely, especialyl for VPN purposes, and I am now back to the stone age of only being able to use IP's since all 8, rather large, Active Directory domains I manage all have the reccomended internal domain naming of '.local'.

Just like Christian, I have tested every possible combination of settings and get same results. Any internal domains that I have split DNS setup for will work just fine, but let me try something ending in .local and it is hosed.

Now I have a 400.00 cell phone. For this level of functionality I could have stuck with Verizon and spent 50 bucks. Great!!!

Would this be Microsoft's fault since it's their VPN that requires .local? You can send feedback to Apple about your issue - http://apple.com/feedback

It isn't vpn that is the issue, per say, but rather DNS name resolution on any Microsoft network that utilizes domains ending in '.local'

In fact, for the almost 10 years since MS came out with Active Directory this is the preferred and reccomended way to name internal domains. You setup domains as '.com' for the outside world and 'domain.local' for your internal world.....using .com as an example.

Apple knew this was a problem with Bonjour on their Mac OS and fixed it. Seems they just haven't bridged the gap over to the Iphone and Itouch yet.

I just got off the phone with support and that was the only suggestion offerred, to use feedback.

Just a blessed shame. I can't even use my in-home wifi and resolve names for my internal home network becuase it follows MS guidelines of Domain.Local

Oh well.

Just to add to 'IPwin' nicely detailed response....
Yes, the Iphone is acting in this manner even if the Iphone is propoerly configured for using the MS network's properly configured internal DNS server. This is in WiFi (private network Wifi) tests and VPN tests (vpn tests using a Public WiFi and 3G network).

Maybe a fix will be out soon, but editing the Search Domains parameter has no effect.