# Work around Android's sneaky DHCP behaviour

**URL:** <https://discourse.pi-hole.net/t/work-around-androids-sneaky-dhcp-behaviour/51114>\
**Category:** Customizing Pi-hole\
**Created:** [November 17, 2021, 1:17pm UTC](https://discourse.pi-hole.net/t/work-around-androids-sneaky-dhcp-behaviour/51114 "2021-11-17T13:17:48Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [November 17, 2021, 3:33pm UTC](https://discourse.pi-hole.net/t/work-around-androids-sneaky-dhcp-behaviour/51114/3 "2021-11-17T15:33:13Z")

</div>

> [@Ben\_Ward](#):
>
> I'd like to see pihole come with an option to enable a second IP address

Pi-hole would only be able to do this if it is the DHCP server.

The workaround for now if you are using Pi-hole as DHCP server is to add a second DNS server assignment in a new dnsmasq configuration file.

> [@Secondary DNS Server for DHCP](https://discourse.pi-hole.net/t/secondary-dns-server-for-dhcp/1874/4):
>
> I have it running in different environments (two of them at an enterprise level, one with more than 100 clients). They all run on Raspberry Pi hardware in various revisions. They never failed so far, so I wouldn't bother too much. A clever idea might be to set up two independent Pi-hole's and (two distinct devices in the same network) and set up those two IPs as "primary" and "secondary" servers. All devices should be able to resolve domains, even if one of them fails for some reason. The cost…

---

_[View the full topic](https://discourse.pi-hole.net/t/work-around-androids-sneaky-dhcp-behaviour/51114)._