# Manually DNS windows, have to manually change DNS every day

**URL:** https://discourse.pi-hole.net/t/manually-dns-windows-have-to-manually-change-dns-every-day/10671
**Category:** Help
**Created:** [July 3, 2018, 4:19pm UTC](https://discourse.pi-hole.net/t/manually-dns-windows-have-to-manually-change-dns-every-day/10671 "2018-07-03T16:19:52Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![RamSet](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/ramset/32/3497_2.png) [@RamSet](https://discourse.pi-hole.net/u/RamSet)
#### Post date: [July 3, 2018, 4:28pm UTC](https://discourse.pi-hole.net/t/manually-dns-windows-have-to-manually-change-dns-every-day/10671/2 "2018-07-03T16:28:15Z")

</div>

You would set-up the Pi-hole IP in your DHCP server to be handed out to the clients automatically.

On the router that is (if your router is the DHCP server/Hadler).  
Then, everything that connects to the network and gets a leased IP, also gets the DNS setting pushed to it.

So all your clients would be set-up as Auto for IP settings on the Network properties.

If your router however (and I fear that this is the case with your device) does not have the ability to push the DNS setting to the clients, you have 2 options:

**a.** Either set the Pi-hole IP at WAN level (DNS setting), OR **b.** (recommended) use the Pi-hole DHCP function and disable the DHCP in the router.  
When using **a.** , all the queries will show as originating from the router (in the query log on the Pi-hole admin interface) and you won't be able to track who's who doing what.  
When using **b.** , you get to see who's requesting what AND your DNS server setting is automatically pushed to the clients.

> [@How do I use Pi-hole's built in DHCP server (and why would I want to)?](https://discourse.pi-hole.net/t/how-do-i-use-pi-holes-built-in-dhcp-server-and-why-would-i-want-to/3026):
>
> Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often [set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245), which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. W…

**One thing to keep in mind.**

If you're using a secondary DNS (in the router under WAN DNS2), there are chances that queries will bleed through it and hence, bypass the Pi-hole restriction.

> [@Why should Pi-hole be my only DNS server?](https://discourse.pi-hole.net/t/why-should-pi-hole-be-my-only-dns-server/3376):
>
> Reduced Ad Blocking Capability The main reason you should Pi-hole as your only DNS server is that you will see increased performance in the blocking of ads. If you have two DNS servers (Pi-hole and something else), your network clients may not always query Pi-hole for name resolution. If a query happens to be answered from a non-Pi-hole DNS server, your block lists will not apply (since that DNS server doesn't know about them). All Queries Need To Go Through Pi-hole First Since other DNS serv…

---

_[View the full topic](https://discourse.pi-hole.net/t/manually-dns-windows-have-to-manually-change-dns-every-day/10671)._