# "\_81.\_https.pi.hole" in query log

**URL:** <https://discourse.pi-hole.net/t/81-https-pi-hole-in-query-log/61269>\
**Category:** Community Help\
**Created:** [February 17, 2023, 2:15pm UTC](https://discourse.pi-hole.net/t/81-https-pi-hole-in-query-log/61269 "2023-02-17T14:15:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ninja\_teabagger](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/n/5f9b8f/32.png) [@ninja\_teabagger](https://discourse.pi-hole.net/u/ninja_teabagger)\
**Post date:** [February 17, 2023, 2:15pm UTC](https://discourse.pi-hole.net/t/81-https-pi-hole-in-query-log/61269/1 "2023-02-17T14:15:14Z")

</div>

Is this anything to be concerned about? I rebuilt Dietpi on a new Proxmox machine last week and set up pi-hole again, this time with unbound. My Desktop PC shows this in the query log whenever I login to [http://pi.hole:81/admin/](http://pi.hole:81/admin/) (I moved admin port to 81). I don't ever remember seeing this before and might be thinking I've configured something wrong somewhere, I'm not attempting to login with https either.

I posted this on Reddit but didn't get much followup answers, It seems all my windows PCs and android phone causes that entry to appear in the query log when I log in to administration. I'm using Chrome & Firefox.

## Expected Behaviour:

Expecting query log to not show that line, as I'm not familiar with seeing it appear.

DietPi 8.14 on a Proxmox VM, 4GB  
Pi-hole version is v5.15.5 (Latest: v5.15.5)  
AdminLTE version is v5.18.4 (Latest: v5.18.4)  
FTL version is v5.21 (Latest: v5.21)

## Actual Behaviour:

See screenshot:

 ![tLSqVAT](https://discourse.pi-hole.net/uploads/default/original/3X/e/f/ef021c4abc3088e57a83d39f5c3861b9004de74f.png)

## Debug Token:

[https://tricorder.pi-hole.net/A8vfon8o/](https://tricorder.pi-hole.net/A8vfon8o/)

---

<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:** [February 17, 2023, 3:53pm UTC](https://discourse.pi-hole.net/t/81-https-pi-hole-in-query-log/61269/3 "2023-02-17T15:53:23Z")

</div>

> [@ninja\_teabagger](#):
>
> Expecting query log to not show that line

Received queries are outside of the control of Pi-hole, and I would not classify this as expected behavior. The client is requesting that domain, and Pi-hole is receiving and processing the request.

The domain does not exist, and Pi-hole correctly returns that result.

Note that these are Type HTTPS queries, not A queries. There is some discussion about this query type in this thread and the referenced link:

> [@What is this “OTHER” category about?](https://discourse.pi-hole.net/t/what-is-this-other-category-about/38490):
>
> Hello guys. First and foremost I haven’t been on the Discourse site for a while so I apologize in advance if this has been touched on already, but a quick search didn’t yield any results. Lately, I’ve noticed a very large amount of queries classified as “OTHER”. Most of these queries were once classified as “A” or “AAAA”. Even “discourse.pi-hole.net” is classified as a “OTHER” query. I’m sure this isn’t affecting blocking in any way, I’m just curious as to what changes took place as I’ve never h…

[https://tools.ietf.org/html/draft-ietf-dnsop-svcb-https-01](https://tools.ietf.org/html/draft-ietf-dnsop-svcb-https-01)

---

<div class="post-metadata">

**Author:** ![ninja\_teabagger](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/n/5f9b8f/32.png) [@ninja\_teabagger](https://discourse.pi-hole.net/u/ninja_teabagger)\
**Post date:** [March 4, 2023, 6:32pm UTC](https://discourse.pi-hole.net/t/81-https-pi-hole-in-query-log/61269/4 "2023-03-04T18:32:46Z")

</div>

Update:

Chrome is my primary browser. It looks like when Chrome or Edge opens [http://pi.hole:81/admin](http://pi.hole:81/admin) it triggers that strange https query to appear in the logs. Change to any port number in the URL and those will show up too. It doesn't happen when using Firefox (ensuring chrome is closed). Also the heavy chatter from times I've never been to the admin panel seems to be coming from the Pihole Browser Extension in Chrome - which also uses the same URL.

I can solve this by using IP address instead of pi.hole at my startpage link and extension settings. But I still have no idea why attempting to resolve the hostname in Chrome or Edge queries the https.

---

<div class="post-metadata">

**Author:** ![chrislph](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/chrislph/32/32723_2.png) [@chrislph](https://discourse.pi-hole.net/u/chrislph)\
**Post date:** [March 4, 2023, 7:20pm UTC](https://discourse.pi-hole.net/t/81-https-pi-hole-in-query-log/61269/5 "2023-03-04T19:20:37Z")

</div>

> [@ninja\_teabagger](#):
>
> But I still have no idea why attempting to resolve the hostname in Chrome or Edge queries the https.

I think Chrome and Edge are issuing these requests to discover any associated records for the domain, to help inform their behaviour when connecting to the domain's services. Whereas using the IP does not require name resolution and so you don't see these queries.

---

<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 25, 2023, 7:20pm UTC](https://discourse.pi-hole.net/t/81-https-pi-hole-in-query-log/61269/6 "2023-03-25T19:20:50Z")

</div>

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