Bring Your Own Technology (BYOT) means an massive influx of mobile devices, such as Droids, iPhones, Kindles, iPads, iTouch, Nexus, Surface and just about any other Internet Protocol apparatus at student can put in his or her book bag. BYOT adds several capacity concerns to network but also contributes to some lesser known issues regarding DNS and DHCP.
In this case, some Android devices do not recognize internal DNS nomenclature – specifically, fully qualified domain names (e.g. device.schoolname.local). This presents a problem because some web based filtering and wireless network controllers usually like to keep track of DNS entries generated after the device successfully obtains an IP address via DHCP. Most importantly, web based authentication mechanisms require that the device prompt the user for active network credentials in order to proceed to network services such as Internet access.
During a recent run-in with a droid device, once successfully connected to the BYOT portion of the wireless network, web based authentication failed. From what our engineering team has ascertained, the droid device does not seem to populate the local DNS suffix field from the DHCP option field. This means that any DNS specific entries for web authorization redirection may fail.
To correct this situation, our team (which utilizes a local Cisco 4404 WLAN controller) configured the Wireless LAN controller name to the fully qualified domain name:
WLAN name current listed as just c4404.
We changed to c4404.schoolname.local, rebooted the controller and then joy!