# DNSMASQ\_WARN

**URL:** <https://discourse.pi-hole.net/t/dnsmasq-warn/72160>\
**Category:** Community Help\
**Created:** [September 4, 2024, 3:13pm UTC](https://discourse.pi-hole.net/t/dnsmasq-warn/72160 "2024-09-04T15:13:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bundy](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bundy/32/37366_2.png) [@Bundy](https://discourse.pi-hole.net/u/Bundy)\
**Post date:** [September 4, 2024, 3:13pm UTC](https://discourse.pi-hole.net/t/dnsmasq-warn/72160/1 "2024-09-04T15:13:02Z")

</div>

I got a DNSMASQ\_WARN error on my Pi-hole. In principle it is solved by checking the option: Potentially dangerous options "allow all sources", right?

If I have not exposed pi-hole to the internet, nothing serious should happen, which I have not done as far as I know since it would be to put the Raspberry Pi IP with port 53 through the router or so I read on the internet.

I also don't understand why I get this error when I have never had large network jumps for it to occur, which apparently the error is when there are subnets or VPNs in your local network, which do not exist at all for now.

On the other hand, would exposing pi-hole to the internet allow it to be used as an ad blocker in some way?, another question that I don't know and I take advantage of the inertia of this post.

Thanks for a future clarification, for now I leave that option checked to rule out configuration errors.

---

<div class="post-metadata">

**Author:** ![nprampage](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/n/71c47a/32.png) [@nprampage](https://discourse.pi-hole.net/u/nprampage)\
**Post date:** [September 5, 2024, 1:59pm UTC](https://discourse.pi-hole.net/t/dnsmasq-warn/72160/2 "2024-09-05T13:59:54Z")

</div>

It would probably help to know the exact error. DNSMASQ\_WARN is just a category of messages; the text following that might provide more helpful information.

---

<div class="post-metadata">

**Author:** ![Bundy](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bundy/32/37366_2.png) [@Bundy](https://discourse.pi-hole.net/u/Bundy)\
**Post date:** [September 5, 2024, 2:34pm UTC](https://discourse.pi-hole.net/t/dnsmasq-warn/72160/3 "2024-09-05T14:34:45Z")

</div>

OK. Well, with the mention option, it disappears, but I can put it back to pass on more information.

---

<div class="post-metadata">

**Author:** ![Bundy](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bundy/32/37366_2.png) [@Bundy](https://discourse.pi-hole.net/u/Bundy)\
**Post date:** [September 14, 2024, 9:19am UTC](https://discourse.pi-hole.net/t/dnsmasq-warn/72160/4 "2024-09-14T09:19:50Z")

</div>

> [@DNSMASQ\_WARN](https://discourse.pi-hole.net/t/dnsmasq-warn/72160/2):
>
> It would probably help to know the exact error. DNSMASQ\_WARN is just a category of messages; the text following that might provide more helpful information.

**Warning in `dnsmasq` core:**  
**Maximum number of concurrent DNS queries reached (max: 150)**

This is the problem, another setting not solved this.

I tried this: [[Resolved] Maximum number of concurrent DNS queries reached - #2 by bombz88](https://discourse.pi-hole.net/t/resolved-maximum-number-of-concurrent-dns-queries-reached/60970/2)

Wating for results...

---

<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:** [October 5, 2024, 9:20am UTC](https://discourse.pi-hole.net/t/dnsmasq-warn/72160/5 "2024-10-05T09:20:32Z")

</div>

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