I have a home network with a Ubuntu Server that handles all DNS and DHCP requests (I have disabled these services in my wireless router). My DHCP server (ISC-DHCP-Server) hands out IP addresses to our various devices based on reservations I have defined in the configuration. It also hands out the search domain, DNS server address, WINS server address, etc, to all clients. The DNS server (bind9) provides local DNS lookup, DNS caching and DNS forwarding (for internet addresses - forwards to Google DNS,

This setup works great for most of my devices (Windows, MAC OSX, iOS) but does not work correctly with Android. When an Android device connects to the wireless network, it receives all of the correct IPs from DHCP. However, all DNS lookups fail. Nevertheless, I can still connect to websites using their IP addresses. All of the other devices are able to look up internal and external DNS records correctly.

This is the kicker. I can get Android to do lookups properly if I configure the network settings manually (in other words, setup a static IP and manually enter the DNS server on the Android client). However, when Android uses DHCP and receives the exact same values I enter manually, it is unable to do the lookups. I can work around this behavior by adding a secondary DNS server ( to the DHCP configuration, but then the Android device only talks to the secondary server and is only able to resolve external, internet addresses but not internal, intranet addresses.

Any thoughts on what might be causing this?


It turns out it was a DHCP configuration on my end. I accidentally had the broadcast address set to the DHCP server IP instead of the last address (255) in the subnet. Changing this and restarting the DHCP service resolved the issue.

  • I was running a Windows Server DNS server and had the same issue. I added the Broadcast DNS configuration option and set it to the last address in t he subnet and DNS resolution for local addresses started working. – Art Oct 11 '16 at 2:13

Not using the DNS sent out by DHCP is a bug in Android.


More/similar info over on StackOverflow: Android Browser hostnames does not get resolved if domain name is not appended

  • Thanks for the info. I have actually ran across those articles while doing some researching. However, in my case Android won't even resolve FQDNs while most people on those threads only complain about having to use FQDNs to resolve. I think there may be another piece to the puzzle in my case. Is this still related to the known Android bug? – gatekeeper6838 Aug 26 '13 at 20:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.