# Dns warning with latest update

**URL:** <https://discourse.pi-hole.net/t/dns-warning-with-latest-update/52465>\
**Category:** Community Help\
**Tags:** v5-0\
**Created:** [January 10, 2022, 11:59pm UTC](https://discourse.pi-hole.net/t/dns-warning-with-latest-update/52465 "2022-01-10T23:59:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![davistw](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/davistw/32/16102_2.png) [@davistw](https://discourse.pi-hole.net/u/davistw)\
**Post date:** [January 10, 2022, 11:59pm UTC](https://discourse.pi-hole.net/t/dns-warning-with-latest-update/52465/1 "2022-01-10T23:59:23Z")

</div>

since the latest update I am getting the below logged as warning in the gui.

DNSMASQ\_WARN Warning in `dnsmasq` core:  
Ignoring domain gvl.is.l-3com.com for DHCP host name ebs-775qf13

This is a machine on my network that is from my sons work domain.  
I am getting tired of having to clean out the warning que one at a time...  
This is new with the latest pihole update.  
Is there a way to turn off these warnings?

---

<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:** [January 11, 2022, 2:29am UTC](https://discourse.pi-hole.net/t/dns-warning-with-latest-update/52465/2 "2022-01-11T02:29:08Z")

</div>

The warnings have always existed in _ **/var/log/pihole.log** _. A change to Pi-hole made them more visible by also printing them into _ **/var/log/pihole-FTL.log** _ and showing them on the dashboard.

[https://github.com/pi-hole/FTL/pull/1243](https://github.com/pi-hole/FTL/pull/1243)

[https://pi-hole.net/2021/12/22/pi-hole-ftl-v5-12-web-v5-9-and-core-v5-7-released](https://pi-hole.net/2021/12/22/pi-hole-ftl-v5-12-web-v5-9-and-core-v5-7-released)

Brief documentation for these warning can be found here:

> **[dnsmasq warnings - Pi-hole documentation](https://docs.pi-hole.net/ftldns/dnsmasq_warn/)**

There is no way to turn off the warnings - they are generated by dnsmasq and Pi-hole shows them all.

To fix it so you no longer get the warning, see this thread:

> [@Ignoring domain CONFIG\_DOMAIN for DHCP host name HOSTNAME](https://discourse.pi-hole.net/t/ignoring-domain-config-domain-for-dhcp-host-name-hostname/52027/8):
>
> I read through several Microsoft documentation pages but nothing really helped. Here is what seems to happen: Windows always uses the primary DNS-suffix when asking for a DHCP lease. It simply ignores the connection-specific one. This one is only used when accessing devices over a given connection. Sounds somewhat useless but matches your observation. The idea could be to add a new file /etc/dnsmasq.d/99-domains.conf and add domain=CONSULTING-AG.local,192.168.2.123 where the CONSULTING-AG.loc…

---

<div class="post-metadata">

**Author:** ![davistw](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/davistw/32/16102_2.png) [@davistw](https://discourse.pi-hole.net/u/davistw)\
**Post date:** [January 17, 2022, 3:31pm UTC](https://discourse.pi-hole.net/t/dns-warning-with-latest-update/52465/3 "2022-01-17T15:31:27Z")

</div>

How about giving he user the capability to filter the messages out or at least select all the messages at once to delete. it is getting to be a pain having to every couple of days select/delete select/delete rinse and repeat.

---

<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:** [February 7, 2022, 3:31pm UTC](https://discourse.pi-hole.net/t/dns-warning-with-latest-update/52465/4 "2022-02-07T15:31:44Z")

</div>

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