# /etc/dnsmasq.d/\* is disabled after upgrading to v6

**URL:** <https://discourse.pi-hole.net/t/etc-dnsmasq-d-is-disabled-after-upgrading-to-v6/76059>\
**Category:** Help\
**Created:** [February 19, 2025, 7:59pm UTC](https://discourse.pi-hole.net/t/etc-dnsmasq-d-is-disabled-after-upgrading-to-v6/76059 "2025-02-19T19:59:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![orb71](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/orb71/32/45651_2.png) [@orb71](https://discourse.pi-hole.net/u/orb71)\
**Post date:** [February 19, 2025, 7:59pm UTC](https://discourse.pi-hole.net/t/etc-dnsmasq-d-is-disabled-after-upgrading-to-v6/76059/1 "2025-02-19T19:59:31Z")

</div>

After upgrading to v6 (docker), I noticed my client received the pihole docker network address as the DNS server due to a `dhcp-helper` in my setup. After troubleshooting, I found that `dhcp-option=option:dns-server,192.168.x.x` was ignored.

A quick look at `pihole.toml` led me to [this post](https://discourse.pi-hole.net/t/etc-dnsmasq-d-files/74393/2) for a solution

Is there another way to pass this option, or do we need to manually re-enable it and leave it ?

Oli

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [February 19, 2025, 8:09pm UTC](https://discourse.pi-hole.net/t/etc-dnsmasq-d-is-disabled-after-upgrading-to-v6/76059/2 "2025-02-19T20:09:25Z")

</div>

> [@orb71](#):
>
> Is there another way to pass this option, or do we need to manually re-enable it and leave it ?

You have some options.

1. add an environment variable (`FTLCONF_misc.dnsmasq_d`) to your compose file, to enable this option;
2. start the container without it and execute the command from the other post to enable `misc.etc_dnsmasq_d`;
3. start the container without it and use the web interface to enable the `misc.etc_dnsmasq_d` option (see image - left side);
4. don't use `misc.etc_dnsmasq_d` option and don't use a volume external files for `dnsmasq`.  
In v6, you can enter `dnsmasq` options via Web Interface using the new `misc.dnsmasq_lines` (see image - right side).

_ **Settings \> All settings** _ page - _Miscellaneous_ tab:

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/8/4/84ca8c44ae8294cafd3dd8b5c022cf9e5fe21089.png)

---

<div class="post-metadata">

**Author:** ![orb71](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/orb71/32/45651_2.png) [@orb71](https://discourse.pi-hole.net/u/orb71)\
**Post date:** [February 23, 2025, 10:41am UTC](https://discourse.pi-hole.net/t/etc-dnsmasq-d-is-disabled-after-upgrading-to-v6/76059/3 "2025-02-23T10:41:32Z")

</div>

I later learned more about it, but thanks for taking the time to answer!

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [March 16, 2025, 10:41am UTC](https://discourse.pi-hole.net/t/etc-dnsmasq-d-is-disabled-after-upgrading-to-v6/76059/4 "2025-03-16T10:41:39Z")

</div>

Closed on March 16, 2025, 10:41am UTC

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
