Dear All,
Find out one article of a lot articles I found to specify that Domain.Local have a lot of issues with Apple and some phones.The .local domain and DNS issues
I found this the hard way, and since I see others have run into the same problem without listing a definite solution, I thought I'd make this easy to find.
OSX (at least 10.2 and on) will not resolve .local names via DNS. lookupd's DNSAgent simply refuses to issue queries for them. This gives the strange situation where nslookup foo.bar.local returns the correct information while ping foo.bar.local returns an 'unknown host' error.
This is documented in Apple's Knowledge Base (article 107174), but if you didn't think to browse the Rendezvous docs for DNS problems, you'd probably never find it. Apple's recommendation is to simply change your domain from .local to .home, .office or .lan. I've done that here, but with well-established kerberos and afs servers in the .local domain, it was anything but simple (or pleasant).
The only other workaround I know of is to populate each Mac's /etc/hosts file with all the local IPs and hostnames (e.g., "10.0.0.1 foo.bar.local foo"), and then change lookupd's search order with the following command (shown on two lines, but the backslash should allow a copy and paste to work):
nicl . -create /locations/lookupd/hosts \
LookupOrder Cache FF DNS NI DSThe tradeoff here is that while names in .local now resolve correctly, you've got the fun of keeping your /etc/hosts files in sync. That's probably why you installed a DNS server in the first place.
Finally, I have no idea how this workaround might affect Rendezvous. I do know that disabling Rendezvous completely had no affect on .local name resolutions.
-----
I had read the KB from Apple site and I do not think that the problem is related to Apple devices.
The problem is in the Mac OS... Multicast DNS is one of the features of Bonjour (formerly "Rendezvous"), included in Mac OS X 10.2 or later. It allows you to connect via Internet protocol (IP) to other computers on a local network by name, rather than a numbered address. This is equal to NetBios name in Microsoft area.
Since your infrastructure will be Microsoft dependable I do not think you have to worry, According to devices like Mobile phone such as I-Phone. You have to configure the public name on it in order to get it work so choosing .local will not affect it.
Most of my customers have splitting DNS and they are working fine without any problems.
I even used IPhone to Sync with Exchnage 2007 in splitting DNS and it is working fine.
The problem is in the Mac OS... Multicast DNS is one of the features of Bonjour (formerly "Rendezvous"), included in Mac OS X 10.2 or later. It allows you to connect via Internet protocol (IP) to other computers on a local network by name, rather than a numbered address. This is equal to NetBios name in Microsoft area.
Since your infrastructure will be Microsoft dependable I do not think you have to worry, According to devices like Mobile phone such as I-Phone. You have to configure the public name on it in order to get it work so choosing .local will not affect it.
Most of my customers have splitting DNS and they are working fine without any problems.
I even used IPhone to Sync with Exchnage 2007 in splitting DNS and it is working fine.
Comments
Post a Comment