Apple Support Communities > Servers and Enterprise Software > Mac OS X Server v10.4 and earlier > Discussions
This discussion is archived
3226 Views 4 Replies Latest reply: Jun 22, 2009 11:46 AM by dmfsantacruz
Check your WAP(s) to see if they have the correct DNS information entered into the configs for them. Think about setting up a secondary DNS server for your local network. It doesn't have to be on OS X server. You can setup a secondary using the ISC bind DNS server on an OS X client box -an old G4 is more than capable of handling hundreds of clients.
Currently Being ModeratedJun 19, 2009 10:23 AM (in response to Mabel O\'Farrell)I have 1 Sonicwall handling basic routing and DHCP. As I mentioned, it is assigning the leopard DNS server as the primary and ISP as secondary. All my other clients are doing fine....MacPro 8-Core, Mac OS X (10.5.7), OSX Server 10.5.7, Final Cut Server
The problem may be that -even though you have DNS servers configured in your DHCP server- that the WAP is handing out its address as the DNS server to wireless clients. Take a look at this post:
for a brief explanation. Although it speaks to the AEBS, many WAPs do the same thing when it comes to DNS resolution. Simply adding the IP of your on-site DNS to the configuration of the WAP may solve the problem.
The fact that laptop wireless clients work assumes that the iPhone runs the same OS as they do. That is not the case. The iPhone's OS is not the same as OS X -it is a variant of OS X- and has long-standing issues with DNS over wireless.