Https:// Top Domain exclusion in API

[frankied210]

I have a sleepnumber bed that sends telemetry data on our sleep habits and I can view that data on the Sleep Number ap.

I see https://prod-dg.sleepiq.sleepnumber.com in my Top Domain List and want to exclude it but when I enter it in, i get the following error

Top Domains/Ads entry https://prod-dg.sleepiq.sleepnumber.com is invalid (use only domains)

.
I think it doesn't like the https:// but excluding it doesn't' result in it being removed either.

Any suggestions on how I can get these removed from the API top domains?

[jfb]

Can you post a screenshot(s) of what you are seeing on your web GUI? Thanks.

[frankied210]

Here's how it appears in the Query list

When I try to put it on the API exclusion list, i get the following error.

If I remove the HTTPS:// and just enter prod-dg.sleepiq.sleepnumber.com in the exclusion, I don't get an errore but, it still shows up as a Top Domain

[Mcat12]

The Sleep Number bed somehow is sending an invalid domain to the DNS server (at least it seems that way). Find the queries it sends in the dnsmasq log (/var/log/pihole.log) and share what you find.

[jfb]

Terminal commands that may help search your log:

sudo grep -i sleepnumber /var/log/pihole.log

or search for queries from that device:

sudo grep -i [IP address here] /var/log/pihole.log

[frankied210]

Here's a excerpt from the log

Oct 11 07:07:02 dnsmasq[13446]: 157 192.168.0.214/51327 query[A] https://prod-dg.sleepiq.sleepnumber.com from 192.168.0.214
Oct 11 07:07:02 dnsmasq[13446]: 157 192.168.0.214/51327 forwarded https://prod-dg.sleepiq.sleepnumber.com to 208.67.220.220
Oct 11 07:07:02 dnsmasq[13446]: 158 192.168.0.214/51327 query[AAAA] https://prod-dg.sleepiq.sleepnumber.com from 192.168.0.214
Oct 11 07:07:02 dnsmasq[13446]: 158 192.168.0.214/51327 forwarded https://prod-dg.sleepiq.sleepnumber.com to 208.67.220.220
Oct 11 07:07:02 dnsmasq[13446]: 157 192.168.0.214/51327 reply https://prod-dg.sleepiq.sleepnumber.com is NXDOMAIN
Oct 11 07:07:02 dnsmasq[13446]: 158 192.168.0.214/51327 reply https://prod-dg.sleepiq.sleepnumber.com is NXDOMAIN
Oct 11 07:07:02 dnsmasq[13446]: 159 192.168.0.214/42348 query[A] https://prod-dg.sleepiq.sleepnumber.com.MyHouse from 192.168.0.214
Oct 11 07:07:02 dnsmasq[13446]: 159 192.168.0.214/42348 forwarded https://prod-dg.sleepiq.sleepnumber.com.MyHouse to 192.168.0.1
Oct 11 07:07:02 dnsmasq[13446]: 160 192.168.0.214/42348 query[AAAA] https://prod-dg.sleepiq.sleepnumber.com.MyHouse from 192.168.0.214
Oct 11 07:07:02 dnsmasq[13446]: 160 192.168.0.214/42348 forwarded https://prod-dg.sleepiq.sleepnumber.com.MyHouse to 192.168.0.1
Oct 11 07:07:02 dnsmasq[13446]: 159 192.168.0.214/42348 reply https://prod-dg.sleepiq.sleepnumber.com.MyHouse is NXDOMAIN
Oct 11 07:07:02 dnsmasq[13446]: 160 192.168.0.214/42348 reply https://prod-dg.sleepiq.sleepnumber.com.MyHouse is NXDOMAIN
Oct 11 07:07:02 dnsmasq[13446]: 161 192.168.0.214/50947 reply prod-dg-legacy.sleepiq.sleepnumber.com is <CNAME>
Oct 11 07:07:02 dnsmasq[13446]: 162 192.168.0.214/50947 reply prod-dg-legacy.sleepiq.sleepnumber.com is <CNAME>
Oct 11 07:22:02 dnsmasq[13731]: 496 192.168.0.214/40126 query[A] https://prod-dg.sleepiq.sleepnumber.com from 192.168.0.214
Oct 11 07:22:02 dnsmasq[13731]: 496 192.168.0.214/40126 forwarded https://prod-dg.sleepiq.sleepnumber.com to 208.67.220.220
Oct 11 07:22:02 dnsmasq[13731]: 497 192.168.0.214/40126 query[AAAA] https://prod-dg.sleepiq.sleepnumber.com from 192.168.0.214
Oct 11 07:22:02 dnsmasq[13731]: 497 192.168.0.214/40126 forwarded https://prod-dg.sleepiq.sleepnumber.com to 208.67.220.220
Oct 11 07:22:02 dnsmasq[13731]: 496 192.168.0.214/40126 reply https://prod-dg.sleepiq.sleepnumber.com is NXDOMAIN
Oct 11 07:22:02 dnsmasq[13731]: 497 192.168.0.214/40126 reply https://prod-dg.sleepiq.sleepnumber.com is NXDOMAIN
Oct 11 07:22:02 dnsmasq[13731]: 498 192.168.0.214/50073 query[A] https://prod-dg.sleepiq.sleepnumber.com.MyHouse from 192.168.0.214
Oct 11 07:22:02 dnsmasq[13731]: 498 192.168.0.214/50073 forwarded https://prod-dg.sleepiq.sleepnumber.com.MyHouse to 192.168.0.1
Oct 11 07:22:02 dnsmasq[13731]: 499 192.168.0.214/50073 query[AAAA] https://prod-dg.sleepiq.sleepnumber.com.MyHouse from 192.168.0.214
Oct 11 07:22:02 dnsmasq[13731]: 499 192.168.0.214/50073 forwarded https://prod-dg.sleepiq.sleepnumber.com.MyHouse to 192.168.0.1
Oct 11 07:22:02 dnsmasq[13731]: 498 192.168.0.214/50073 reply https://prod-dg.sleepiq.sleepnumber.com.MyHouse is NXDOMAIN
Oct 11 07:22:02 dnsmasq[13731]: 499 192.168.0.214/50073 reply https://prod-dg.sleepiq.sleepnumber.com.MyHouse is NXDOMAIN
Oct 11 07:22:02 dnsmasq[13731]: 500 192.168.0.214/56121 reply prod-dg-legacy.sleepiq.sleepnumber.com is <CNAME>
Oct 11 07:22:02 dnsmasq[13731]: 501 192.168.0.214/56121 reply prod-dg-legacy.sleepiq.sleepnumber.com is <CNAME>
Oct 11 07:37:02 dnsmasq[13731]: 1286 192.168.0.214/56801 query[A] https://prod-dg.sleepiq.sleepnumber.com from 192.168.0.214
Oct 11 07:37:02 dnsmasq[13731]: 1286 192.168.0.214/56801 forwarded https://prod-dg.sleepiq.sleepnumber.com to 208.67.222.222
Oct 11 07:37:02 dnsmasq[13731]: 1287 192.168.0.214/56801 query[AAAA] https://prod-dg.sleepiq.sleepnumber.com from 192.168.0.214
Oct 11 07:37:02 dnsmasq[13731]: 1287 192.168.0.214/56801 forwarded https://prod-dg.sleepiq.sleepnumber.com to 208.67.222.222
Oct 11 07:37:02 dnsmasq[13731]: 1286 192.168.0.214/56801 reply https://prod-dg.sleepiq.sleepnumber.com is NXDOMAIN
Oct 11 07:37:02 dnsmasq[13731]: 1287 192.168.0.214/56801 reply https://prod-dg.sleepiq.sleepnumber.com is NXDOMAIN
Oct 11 07:37:02 dnsmasq[13731]: 1288 192.168.0.214/51297 query[A] https://prod-dg.sleepiq.sleepnumber.com.MyHouse from 192.168.0.214
Oct 11 07:37:02 dnsmasq[13731]: 1288 192.168.0.214/51297 cached https://prod-dg.sleepiq.sleepnumber.com.MyHouse is NXDOMAIN
Oct 11 07:37:02 dnsmasq[13731]: 1289 192.168.0.214/51297 query[AAAA] https://prod-dg.sleepiq.sleepnumber.com.MyHouse from 192.168.0.214
Oct 11 07:37:02 dnsmasq[13731]: 1289 192.168.0.214/51297 cached https://prod-dg.sleepiq.sleepnumber.com.MyHouse is NXDOMAIN
Oct 11 07:37:02 dnsmasq[13731]: 1290 192.168.0.214/52595 reply prod-dg-legacy.sleepiq.sleepnumber.com is <CNAME>
Oct 11 07:37:02 dnsmasq[13731]: 1291 192.168.0.214/52595 reply prod-dg-legacy.sleepiq.sleepnumber.com is <CNAME>

[Mcat12]

Pi-hole is acting correctly in this case. It received a query from a client, forwarded it up, and since it was a bad request, the upstream sent an NXDOMAIN response, which Pi-hole returned to the client. You can try manually entering the URL into this /etc/pihole/setupVars.conf setting:

API_EXCLUDE_DOMAINS=https://prod-dg.sleepiq.sleepnumber.com

[frankied210]

Perfect. Manually adding it to setupVars.conf worked!

Thanks!

[jfb]

A further option if you want to never see this client in your Pi-Hole and you are using the DHCP server in your Pi-Hole - exclude that client from Pi-Hole and give that client a third party DNS address.

Things you can do with dnsmasq!

I came up with some stuff that eases things a little bit with my Pi-Hole life. Some of the ideas here, I gathered from around the internet. I wanted to share my findings. These configs are to be placed in /etc/dnsmasq.d I do realize that these could easily be combined into a single 04-custom.conf, but for the ease of teaching myself things I can do with this,, I like them seperate. Bypass Pihole by MAC Address What this Does: Find the MAC Address of the device that you want to skip pihole, …

[frankied210]

I do have a separate VLAN for my "No-Pihole" clients but, it's currently restricted to wired clients only. I didn't wan't to set up a separate SSID for this one wireless client just to give a different DNS via DHCP for this one nuisance client.. I even consider how I might manually assign DNS to the bed but, there isn't exactly a customer facing user interface for that.