# Https-dns-proxy canary domain persistance

**URL:** <https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967>\
**Category:** Installing and Using OpenWrt\
**Created:** [October 17, 2022, 11:26pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967 "2022-10-17T23:26:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhester72](https://forum.openwrt.org/letter_avatar/rhester72/32/5_5575768a8748004e209b776fc1b2916d.png) [@rhester72](https://forum.openwrt.org/u/rhester72)\
**Post date:** [October 17, 2022, 11:26pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/1 "2022-10-17T23:26:13Z")

</div>

When canary domains are enabled (as per default) and https-dns-proxy is started, canary domains are (correctly) added to /etc/config/dhcp as server entries.

However, they are _also_ added as doh\_backup\_server entries, which means that once https-dns-proxy is stopped (or removed), the canary domains persist as server entries.

I'm assuming this is not intended behavior - @stangri, can you confirm?

I do _not_ think this is related to a similar topic of canary domain duplication found here:

> [@How to remove domains from DNS Query Redirection?](https://forum.openwrt.org/t/how-to-remove-domains-from-dns-query-redirection/138647):
>
> Hi! After updating luci-app-https-dns-proxy, domains appeared in Redirect DNS requests /mask.icloud.com/ and /mask-h2.icloud.com/ and if they are deleted and the https-dns-proxy service is restarted, they appear again, how to get rid of them since I don't need it ?

---

<div class="post-metadata">

**Author:** ![stangri](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stangri/32/58_2.png) [@stangri](https://forum.openwrt.org/u/stangri)\
**Post date:** [October 17, 2022, 11:58pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/2 "2022-10-17T23:58:31Z")

</div>

If the canary domains exist in your config before `https-dns-proxy` is started, they are backed up and restored on service stop.

---

<div class="post-metadata">

**Author:** ![rhester72](https://forum.openwrt.org/letter_avatar/rhester72/32/5_5575768a8748004e209b776fc1b2916d.png) [@rhester72](https://forum.openwrt.org/u/rhester72)\
**Post date:** [October 18, 2022, 1:28am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/3 "2022-10-18T01:28:22Z")

</div>

Steps to reproduce:

- Stop https-dns-proxy
- Check for and remove any canary domains from /etc/config/dhcp
- Start https-dns-proxy
- Stop https-dns-proxy

Observe the presence of the canary domains as active with service stopped and never having been otherwise active without https-dns-proxy.

---

<div class="post-metadata">

**Author:** ![stangri](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stangri/32/58_2.png) [@stangri](https://forum.openwrt.org/u/stangri)\
**Post date:** [October 19, 2022, 8:49am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/4 "2022-10-19T08:49:30Z")

</div>

Please confirm the version of `https-dns-proxy` you're using.

---

<div class="post-metadata">

**Author:** ![tapper](https://forum.openwrt.org/user_avatar/forum.openwrt.org/tapper/32/3012_2.png) [@tapper](https://forum.openwrt.org/u/tapper)\
**Post date:** [October 19, 2022, 9:00am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/5 "2022-10-19T09:00:27Z")

</div>

What is a canary domains?

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [October 19, 2022, 9:19am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/6 "2022-10-19T09:19:44Z")

</div>

google _canary domain_ ?

TLDR; used to check if internet access works

---

<div class="post-metadata">

**Author:** ![slh](https://forum.openwrt.org/user_avatar/forum.openwrt.org/slh/32/113591_2.png) [@slh](https://forum.openwrt.org/u/slh)\
**Post date:** [October 19, 2022, 9:21am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/7 "2022-10-19T09:21:24Z")

</div>

A central way for the network administrator to tell connected clients (respectively their webbrowsers) not to use DoH, e.g. because local domain resolution is needed (also useful for adblocking), like for company intranets, campus resources etc.

Currently `use-application-dns.net` is used for that, resolving this domain with `NXDOMAIN` in your network tells browsers to disable DoH.

> **[Canary domain - use-application-dns.net | Firefox Help](https://support.mozilla.org/en-US/kb/canary-domain-use-application-dnsnet)**
>
> Network administrators may configure their networks to modify DNS requests for the following special-purpose domain, called a ''canary domain''.

---

<div class="post-metadata">

**Author:** ![rhester72](https://forum.openwrt.org/letter_avatar/rhester72/32/5_5575768a8748004e209b776fc1b2916d.png) [@rhester72](https://forum.openwrt.org/u/rhester72)\
**Post date:** [October 19, 2022, 2:27pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/8 "2022-10-19T14:27:43Z")

</div>

https-dns-proxy - 2022-08-12-1

I just noticed an upgrade available, will give that a try.

EDIT: Behavior persists in 2022-10-15-1, same method to reproduce

---

<div class="post-metadata">

**Author:** ![stangri](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stangri/32/58_2.png) [@stangri](https://forum.openwrt.org/u/stangri)\
**Post date:** [October 19, 2022, 11:53pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/9 "2022-10-19T23:53:41Z")

</div>

Great find! After I made the canary domains user-configurable, I forgot to rewrite the service stop function to support that! Will be fixed in the next release.

---

<div class="post-metadata">

**Author:** ![stangri](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stangri/32/58_2.png) [@stangri](https://forum.openwrt.org/u/stangri)\
**Post date:** [October 20, 2022, 5:25am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/10 "2022-10-20T05:25:57Z")

</div>

PRs: [https://github.com/openwrt/packages/pull/19635](https://github.com/openwrt/packages/pull/19635) [https://github.com/openwrt/packages/pull/19636](https://github.com/openwrt/packages/pull/19636)

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [October 20, 2022, 11:09am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/11 "2022-10-20T11:09:04Z")

</div>

Collected errors:  
resolve\_conffiles: Existing conffile /etc/config/https-dns-proxy is different from the conffile in the new package.  
The new conffile will be placed at /etc/config/https-dns-proxy-opkg.

this is when updating the package and two files appear in the config  
https-dns-proxy and https-dns-proxy-opkg

---

<div class="post-metadata">

**Author:** ![stangri](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stangri/32/58_2.png) [@stangri](https://forum.openwrt.org/u/stangri)\
**Post date:** [October 20, 2022, 11:39am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/12 "2022-10-20T11:39:56Z")

</div>

Yes, this is how opkg works when you have a config file for the package being installed.

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [October 20, 2022, 12:40pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/13 "2022-10-20T12:40:30Z")

</div>

reset the settings and the package installed without errors.

dns did not work after changing the IP address of the wan on the first router, and does not work until you restart this service.  
when the IP address of the wan of the first router changes, dns refuses to work and I don't know what to do

---

<div class="post-metadata">

**Author:** ![rhester72](https://forum.openwrt.org/letter_avatar/rhester72/32/5_5575768a8748004e209b776fc1b2916d.png) [@rhester72](https://forum.openwrt.org/u/rhester72)\
**Post date:** [October 20, 2022, 1:46pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/14 "2022-10-20T13:46:37Z")

</div>

Did you intend to set the version to dev-test as part of the pull request?

---

<div class="post-metadata">

**Author:** ![stangri](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stangri/32/58_2.png) [@stangri](https://forum.openwrt.org/u/stangri)\
**Post date:** [October 20, 2022, 10:30pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/15 "2022-10-20T22:30:54Z")

</div>

Yes, it's intentional (to indicate that the init script wasn't installed by opkg), it's updated to the actual version in the Makefile/thru the opkg install.

---

<div class="post-metadata">

**Author:** ![rhester72](https://forum.openwrt.org/letter_avatar/rhester72/32/5_5575768a8748004e209b776fc1b2916d.png) [@rhester72](https://forum.openwrt.org/u/rhester72)\
**Post date:** [October 21, 2022, 1:48am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/16 "2022-10-21T01:48:58Z")

</div>

Ah, learned something new - thank you! It works fine. =)

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [October 21, 2022, 8:57am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/17 "2022-10-21T08:57:57Z")

</div>

began to work worse, the service restarts for a long time, it thinks for a long time

---

<div class="post-metadata">

**Author:** ![rhester72](https://forum.openwrt.org/letter_avatar/rhester72/32/5_5575768a8748004e209b776fc1b2916d.png) [@rhester72](https://forum.openwrt.org/u/rhester72)\
**Post date:** [October 21, 2022, 11:58am UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/18 "2022-10-21T11:58:13Z")

</div>

What is the output of this?

time /etc/init.d/https-dns-proxy restart

---

<div class="post-metadata">

**Author:** ![fkl7834456](https://forum.openwrt.org/letter_avatar/fkl7834456/32/5_5575768a8748004e209b776fc1b2916d.png) [@fkl7834456](https://forum.openwrt.org/u/fkl7834456)\
**Post date:** [October 21, 2022, 1:05pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/19 "2022-10-21T13:05:29Z")

</div>

By asking this question, is there anything you can do to help, or are you just keeping the conversation going?

---

<div class="post-metadata">

**Author:** ![rhester72](https://forum.openwrt.org/letter_avatar/rhester72/32/5_5575768a8748004e209b776fc1b2916d.png) [@rhester72](https://forum.openwrt.org/u/rhester72)\
**Post date:** [October 21, 2022, 2:33pm UTC](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967/20 "2022-10-21T14:33:30Z")

</div>

You reported a problem. I'm trying to confirm the problem. If you don't want help, that's OK too.

[Next page](https://forum.openwrt.org/t/https-dns-proxy-canary-domain-persistance/139967.md?page=2)
