I am almost sure because in logread | grep dnsmasq I see:
https-dns-proxy restarting dnsmasq on config update
Failed to create listening socket. Address 127.0.0.1 already in use
I need both services and I do not know what to do. I only need dnsmasq for lan dhcp and nothing more.
UPD: I am pretty sure now. I removed https-dns-proxy and dnsmasq now start in normal mode. May be there are some actions I need to perform to solve their conflict?
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/dhcp
cat /etc/config/https-dns-proxy
Here is is, yet I no longer have https-dns-proxy so I guess there is no point in this?
root@OpenWrt:~# ubus call system board{"kernel": "6.6.95","hostname": "OpenWrt","system": "Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz","model": "ASUSTeK Computer INC. P5QL-ASUS-SE","board_name": "asustek-computer-inc-p5ql-asus-se","rootfs_type": "ext4","release": {"distribution": "OpenWrt","version": "24.10-SNAPSHOT","revision": "r28759-49fdb75c7b","target": "x86/64","description": "OpenWrt 24.10-SNAPSHOT r28759-49fdb75c7b","builddate": "1752173357"}}root@OpenWrt:~# cat /etc/config/network
config interface 'loopback'option device 'lo'option proto 'static'option ipaddr '127.0.0.1'option netmask '255.0.0.0'
config globals 'globals'option ula_prefix 'fd59:579f:cf82::/48'
config deviceoption name 'br-lan'option type 'bridge'list ports 'eth0'
config interface 'lan'option device 'br-lan'option proto 'static'option ipaddr '192.168.5.1'option netmask '255.255.255.0'option ip6assign '60'
config interface 'wan'option device 'eth1'option proto 'dhcp'
config interface 'wan6'option device 'eth1'option proto 'dhcpv6'
root@OpenWrt:~# cat /etc/config/dhcp
config dnsmasqoption domainneeded '1'option boguspriv '1'option filterwin2k '0'option localise_queries '1'option rebind_protection '1'option rebind_localhost '1'option local '/lan/'option domain 'lan'option expandhosts '1'option nonegcache '0'option cachesize '1000'option authoritative '1'option readethers '1'option leasefile '/tmp/dhcp.leases'option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'option nonwildcard '1'option localservice '1'option ednspacket_max '1232'option filter_aaaa '0'option filter_a '0'list server '/mask.icloud.com/'list server '/mask-h2.icloud.com/'list server '/use-application-dns.net/'list server '127.0.0.1#5053'list server '127.0.0.1#5054'
config dhcp 'lan'option interface 'lan'option start '100'option limit '150'option leasetime '12h'option dhcpv4 'server'option dhcpv6 'server'option ra 'server'option ra_slaac '1'list ra_flags 'managed-config'list ra_flags 'other-config'
config dhcp 'wan'option interface 'wan'option ignore '1'
config odhcpd 'odhcpd'option maindhcp '0'option leasefile '/tmp/hosts/odhcpd'option leasetrigger '/usr/sbin/odhcpd-update'option loglevel '4'
root@OpenWrt:~# cat /etc/config/https-dns-proxycat: can't open '/etc/config/https-dns-proxy': No such file or directoryroot@OpenWrt:~#
May be I need to switch to another solution, like dnsmasq with DoH or Pi-hole?
try reinstalling it.... (if you want to use it and to provide debugging of what you reported)
opkg update
opkg install https-dns-proxy
or apk
apk update
apk add https-dns-proxy
I personally don't have this problem on my system, but if you don't provide more details, we won't be able to help you...
for example like this (I restart the services and look in the logs for what you said):
/etc/init.d/dnsmasq restart; sleep 5; /etc/init.d/https-dns-proxy restart
output:
udhcpc: started, v1.36.1
udhcpc: broadcasting discover
udhcpc: no lease, failing
udhcpc: started, v1.36.1
udhcpc: broadcasting discover
udhcpc: no lease, failing
udhcpc: started, v1.36.1
udhcpc: broadcasting discover
udhcpc: no lease, failing
Starting https-dns-proxy 2025.05.11-r1 instances âś“
Setting trigger for wan âś“
logread | grep "Failed"
output = null
ps: Please format the configuration files better; they are unreadable.
Correct example (I chose to use quad9 instead of "Cloudflare" but there are no anomalies):
cat /etc/config/https-dns-proxy
config main 'config'
option canary_domains_icloud '1'
option canary_domains_mozilla '1'
option dnsmasq_config_update '*'
option force_dns '1'
list force_dns_port '53'
list force_dns_port '853'
option procd_trigger_wan6 '0'
config https-dns-proxy
option resolver_url 'https://dns.quad9.net/dns-query'
option bootstrap_dns '9.9.9.9,149.112.112.112'
option listen_addr '127.0.0.1'
option listen_port '5052'
option user 'nobody'
option group 'nogroup'
What is listening on port 53 then?
netstat -lnptu | grep :53
My guess would be that in the /etc/config/https-dns-proxy you’ve manually set one of the instance’s listen port to 53.
So when you successfully start https-dns-proxy instance, the dnsmasq can no longer start.
Solution: leave the listen address and listen port for the instance settings empty and https-dns-proxy will auto-assign ports to its instances starting from 5053 and up.
Many thanks. I never configure https-dns-proxy manually, all values are in default.
and WHAT PROCESS is listening on port 53 then?
Sorry, I was a bit busy. I make a clean install of my OpenWRT-Build and here is all logs I have assembled as all honorable members of this community requested:
first I typed:
/etc/init.d/dnsmasq status and it was not running so problem still exists
then I collect all other info
logread | grep dnsmasq
Fri Oct 10 08:55:53 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 08:55:53 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 08:55:58 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 08:55:58 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 08:56:03 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 08:56:03 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 08:56:08 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 08:56:08 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 08:56:13 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 08:56:13 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 08:56:13 2025 daemon.info procd: Instance dnsmasq::cfg01411c s in a crash loop 6 crashes, 0 seconds since last crash
Fri Oct 10 09:03:17 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 09:03:17 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 09:03:17 2025 daemon.info procd: Instance dnsmasq::cfg01411c s in a crash loop 7 crashes, 0 seconds since last crash
Fri Oct 10 09:03:21 2025 user.notice https-dns-proxy [5519]: Updating dnsmasq config âś“
Fri Oct 10 09:03:24 2025 user.notice https-dns-proxy [5519]: Restarting dnsmasq on_config_update âś“
Fri Oct 10 09:03:24 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 09:03:24 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 09:03:29 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 09:03:29 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 09:03:34 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 09:03:34 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 09:03:39 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 09:03:39 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 09:03:44 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 09:03:44 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 09:03:49 2025 daemon.crit dnsmasq[1]: failed to create listening socket for 127.0.0.1: Address in use
Fri Oct 10 09:03:49 2025 daemon.crit dnsmasq[1]: FAILED to start up
Fri Oct 10 09:03:49 2025 daemon.info procd: Instance dnsmasq::cfg01411c s in a crash loop 6 crashes, 0 seconds since last crash
netstat -lnptu | grep 53 (doh-client of https-dns-proxy occupy port 53 as I understand)
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 4066/doh-client
tcp 0 0 127.0.0.1:8053 0.0.0.0:* LISTEN 4067/doh-server
tcp 0 0 127.0.0.1:5380 0.0.0.0:* LISTEN 4066/doh-client
tcp 0 0 ::1:8053 :::* LISTEN 4067/doh-server
tcp 0 0 ::1:5380 :::* LISTEN 4066/doh-client
tcp 0 0 ::1:53 :::* LISTEN 4066/doh-client
udp 0 0 127.0.0.1:5053 0.0.0.0:* 5843/https-dns-prox
udp 0 0 127.0.0.1:53 0.0.0.0:* 4066/doh-client
udp 0 0 127.0.0.1:5380 0.0.0.0:* 4066/doh-client
udp 0 0 ::1:53 :::* 4066/doh-client
udp 0 0 ::1:5380 :::* 4066/doh-client
ubus call system board
{
"kernel": "6.6.95",
"hostname": "OpenWrt",
"system": "Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz",
"model": "ASUSTeK Computer INC. P5QL-ASUS-SE",
"board_name": "asustek-computer-inc-p5ql-asus-se",
"rootfs_type": "ext4",
"release": {
"distribution": "OpenWrt",
"version": "24.10-SNAPSHOT",
"revision": "r28759-49fdb75c7b",
"target": "x86/64",
"description": "OpenWrt 24.10-SNAPSHOT r28759-49fdb75c7b",
"builddate": "1752173357"
}
}
/etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdd0:a7ec:d8c6::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option device 'eth1'
option proto 'dhcp'
config interface 'wan6'
option device 'eth1'
option proto 'dhcpv6'
/etc/config/dhcp
config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option nonwildcard '1'
option localservice '1'
option ednspacket_max '1232'
option filter_aaaa '0'
option filter_a '0'
option doh_backup_noresolv '-1'
option noresolv '1'
list doh_backup_server ''
list server '/mask.icloud.com/'
list server '/mask-h2.icloud.com/'
list server '/use-application-dns.net/'
list server '127.0.0.1#5053'
list server '127.0.0.1#5054'
list doh_server '127.0.0.1#5053'
list doh_server '127.0.0.1#5054'
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
option ra_slaac '1'
list ra_flags 'managed-config'
list ra_flags 'other-config'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
/etc/config/https-dns-proxy
config main 'config'
option canary_domains_icloud '1'
option canary_domains_mozilla '1'
option dnsmasq_config_update '*'
option force_dns '1'
list force_dns_port '53'
list force_dns_port '853'
# ports listed below are used by some
# of the dnscrypt-proxy v1 resolvers
# list force_dns_port '553'
# list force_dns_port '1443'
# list force_dns_port '4343'
# list force_dns_port '4434'
# list force_dns_port '5443'
# list force_dns_port '8443'
list procd_fw_src_interfaces 'lan'
option procd_trigger_wan6 '0'
config https-dns-proxy
option bootstrap_dns '1.1.1.1,1.0.0.1'
option resolver_url 'https://cloudflare-dns.com/dns-query'
option listen_addr '127.0.0.1'
option listen_port '5053'
option user 'nobody'
option group 'nogroup'
config https-dns-proxy
option bootstrap_dns '8.8.8.8,8.8.4.4'
option resolver_url 'https://dns.google/dns-query'
option listen_addr '127.0.0.1'
option listen_port '5054'
option user 'nobody'
option group 'nogroup'
I hope I provide all necessary info. I had to force-remov https-dns-proxy so that I could connect to OpenWRT instance via Putty. But if it is necessary I will reinstall it again
doh-client is listening on port 53.
Thats your config, not somebody elses made problem.
My be I am to blame, yet I did not edit any config manually. All values are in default options.
I must say that in 23.05 I did not notice such behaviour of https-dns-proxy or at least not so often
Have you installed anything else?
Please list installed packages...
opkg list-installed; which doh-client
in my system only "dnsmasq" is listening on 53 so the "netstat -lnptu | grep 53" command only reports "dnsmasq" (and I installed "https-dns-proxy" and it works)
ps: doh-client (not installed as a dependency of https-dns-proxy)
opkg whatdepends https-dns-proxy
Root set:
https-dns-proxy
What depends on root set
luci-app-https-dns-proxy 2025.05.11-r4 depends on https-dns-proxy
opkg info https-dns-proxy
Package: https-dns-proxy
Version: 2025.05.11-r1
Depends: libc, libcares, libcurl4, libev, ca-bundle, jsonfilter, resolveip
Conflicts: https_dns_proxy
Status: install ok installed
Section: net
Architecture: arm_cortex-a7_neon-vfpv4
Size: 24242
Filename: https-dns-proxy_2025.05.11-r1_arm_cortex-a7_neon-vfpv4.ipk
Conffiles:
/etc/config/https-dns-proxy 21eed459ec0268bd6c69c9b8fcfc66c10f06f2b2aa997a99d710777cc56f5bb0
Description: Light-weight DNS-over-HTTPS, non-caching translation proxy for the RFC 8484 DoH standard.
It receives regular, unencrypted (UDP) DNS requests and resolves them via DoH resolver.
Please see https://docs.openwrt.melmac.net/https-dns-proxy/ for more information.
Installed-Time: 1750711236
may be doh-client is part of https-dns-proxy package so tiny that is is not listen in package list.
here is opkg list-installed
alsa-lib - 1.2.11-r1
amd64-microcode - 20241110-r2
amdgpu-firmware - 20241110-r2
base-files - 1661~49fdb75c7b
blkid - 2.40.2-r1
bnx2-firmware - 20241110-r2
busybox - 1.36.1-r2
ca-bundle - 20241223-r1
cgi-io - 2022.08.10~901b0f04-r21
chat - 2.5.1-r1
comgt - 0.32-r36
comgt-ncm - 0.32-r36
curl - 8.12.1-r1
dmesg - 2.40.2-r1
dns-over-https - 2.3.0-r2
dnsmasq - 2.90-r4
dnsproxy - 0.75.0-r1
dropbear - 2024.86-r1
e2fsprogs - 1.47.0-r2
fdisk - 2.40.2-r1
fdk-aac - 2.0.1-r5
ffmpeg - 6.1.3-r1
firewall4 - 2024.12.18~18fc0ead-r1
fstools - 2024.07.14~408c2cc4-r1
fwtool - 2019.11.12~8f7fe925-r1
getrandom - 2024.04.26~85f10530-r1
glib2 - 2.82.0-r1
grep - 3.11-r1
grub2 - 2.12-r1
grub2-bios-setup - 2.12-r1
grub2-efi - 2.12-r1
hostapd-common - 2024.09.15~5ace39b0-r2
https-dns-proxy - 2025.10.07-r1
hwinfo - 21.71-r4
i915-firmware-dmc - 20241110-r2
intel-microcode - 20250211-r1
ip-tiny - 6.11.0-r1
iw - 6.9-r1
iwinfo - 2024.10.20~b94f066e-r1
jansson4 - 2.14-r3
jshn - 2024.12.19~3868f47c-r1
jsonfilter - 2025.04.18~8a86fb78-r1
kernel - 6.6.95~a3aff4bc8aa816ce4ab9482d7a9b8ef4-r1
kmod-acpi-video - 6.6.95-r1
kmod-amd-xgbe - 6.6.95-r1
kmod-asn1-decoder - 6.6.95-r1
kmod-asn1-encoder - 6.6.95-r1
kmod-ata-ahci - 6.6.95-r1
kmod-ata-core - 6.6.95-r1
kmod-atl1 - 6.6.95-r1
kmod-atl1c - 6.6.95-r1
kmod-atl1e - 6.6.95-r1
kmod-atl2 - 6.6.95-r1
kmod-backlight - 6.6.95-r1
kmod-bnx2 - 6.6.95-r1
kmod-button-hotplug - 6.6.95-r3
kmod-cfg80211 - 6.6.95.6.12.6-r2
kmod-crypto-acompress - 6.6.95-r1
kmod-crypto-aead - 6.6.95-r1
kmod-crypto-arc4 - 6.6.95-r1
kmod-crypto-authenc - 6.6.95-r1
kmod-crypto-cbc - 6.6.95-r1
kmod-crypto-ccm - 6.6.95-r1
kmod-crypto-cmac - 6.6.95-r1
kmod-crypto-crc32c - 6.6.95-r1
kmod-crypto-ctr - 6.6.95-r1
kmod-crypto-cts - 6.6.95-r1
kmod-crypto-deflate - 6.6.95-r1
kmod-crypto-des - 6.6.95-r1
kmod-crypto-ecb - 6.6.95-r1
kmod-crypto-echainiv - 6.6.95-r1
kmod-crypto-gcm - 6.6.95-r1
kmod-crypto-geniv - 6.6.95-r1
kmod-crypto-gf128 - 6.6.95-r1
kmod-crypto-ghash - 6.6.95-r1
kmod-crypto-hash - 6.6.95-r1
kmod-crypto-hmac - 6.6.95-r1
kmod-crypto-lib-chacha20 - 6.6.95-r1
kmod-crypto-lib-chacha20poly1305 - 6.6.95-r1
kmod-crypto-lib-curve25519 - 6.6.95-r1
kmod-crypto-lib-poly1305 - 6.6.95-r1
kmod-crypto-manager - 6.6.95-r1
kmod-crypto-md5 - 6.6.95-r1
kmod-crypto-null - 6.6.95-r1
kmod-crypto-rng - 6.6.95-r1
kmod-crypto-seqiv - 6.6.95-r1
kmod-crypto-sha1 - 6.6.95-r1
kmod-crypto-sha256 - 6.6.95-r1
kmod-crypto-sha3 - 6.6.95-r1
kmod-crypto-sha512 - 6.6.95-r1
kmod-crypto-user - 6.6.95-r1
kmod-dax - 6.6.95-r1
kmod-dm - 6.6.95-r1
kmod-dma-buf - 6.6.95-r1
kmod-dnsresolver - 6.6.95-r1
kmod-drm - 6.6.95-r1
kmod-drm-buddy - 6.6.95-r1
kmod-drm-display-helper - 6.6.95-r1
kmod-drm-exec - 6.6.95-r1
kmod-drm-i915 - 6.6.95-r1
kmod-drm-kms-helper - 6.6.95-r1
kmod-drm-suballoc-helper - 6.6.95-r1
kmod-drm-ttm - 6.6.95-r1
kmod-drm-ttm-helper - 6.6.95-r1
kmod-dwmac-intel - 6.6.95-r1
kmod-e1000 - 6.6.95-r1
kmod-e1000e - 6.6.95-r1
kmod-fb - 6.6.95-r1
kmod-fb-cfb-copyarea - 6.6.95-r1
kmod-fb-cfb-fillrect - 6.6.95-r1
kmod-fb-cfb-imgblt - 6.6.95-r1
kmod-fb-sys-fops - 6.6.95-r1
kmod-fb-sys-ram - 6.6.95-r1
kmod-fixed-phy - 6.6.95-r1
kmod-forcedeth - 6.6.95-r1
kmod-fs-exportfs - 6.6.95-r1
kmod-fs-ext4 - 6.6.95-r1
kmod-fs-nfs - 6.6.95-r1
kmod-fs-nfs-common - 6.6.95-r1
kmod-fs-nfs-common-rpcsec - 6.6.95-r1
kmod-fs-nfs-v4 - 6.6.95-r1
kmod-fs-nfsd - 6.6.95-r1
kmod-fs-vfat - 6.6.95-r1
kmod-gre - 6.6.95-r1
kmod-gre6 - 6.6.95-r1
kmod-hid - 6.6.95-r1
kmod-hid-generic - 6.6.95-r1
kmod-hwmon-core - 6.6.95-r1
kmod-i2c-algo-bit - 6.6.95-r1
kmod-i2c-core - 6.6.95-r1
kmod-igb - 6.6.95-r1
kmod-igc - 6.6.95-r1
kmod-input-core - 6.6.95-r1
kmod-input-evdev - 6.6.95-r1
kmod-ip6-tunnel - 6.6.95-r1
kmod-ipip - 6.6.95-r1
kmod-ipsec - 6.6.95-r1
kmod-ipsec4 - 6.6.95-r1
kmod-ipsec6 - 6.6.95-r1
kmod-iptunnel - 6.6.95-r1
kmod-iptunnel4 - 6.6.95-r1
kmod-iptunnel6 - 6.6.95-r1
kmod-ixgbe - 6.6.95-r1
kmod-keys-encrypted - 6.6.95-r1
kmod-keys-trusted - 6.6.95-r1
kmod-l2tp - 6.6.95-r1
kmod-lib-crc-ccitt - 6.6.95-r1
kmod-lib-crc16 - 6.6.95-r1
kmod-lib-crc32c - 6.6.95-r1
kmod-lib-zlib-deflate - 6.6.95-r1
kmod-lib-zlib-inflate - 6.6.95-r1
kmod-libphy - 6.6.95-r1
kmod-mac80211 - 6.6.95.6.12.6-r2
kmod-mdio - 6.6.95-r1
kmod-mdio-devres - 6.6.95-r1
kmod-media-controller - 6.6.95-r1
kmod-mii - 6.6.95-r1
kmod-mmc - 6.6.95-r1
kmod-mt76-connac - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt76-core - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt76-sdio - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt76-usb - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt7921-common - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt7921-firmware - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt7921e - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt7921s - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt7921u - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt792x-common - 6.6.95.2025.02.14~e5fef138-r1
kmod-mt792x-usb - 6.6.95.2025.02.14~e5fef138-r1
kmod-net-selftests - 6.6.95-r1
kmod-nf-conntrack - 6.6.95-r1
kmod-nf-conntrack6 - 6.6.95-r1
kmod-nf-flow - 6.6.95-r1
kmod-nf-log - 6.6.95-r1
kmod-nf-log6 - 6.6.95-r1
kmod-nf-nat - 6.6.95-r1
kmod-nf-reject - 6.6.95-r1
kmod-nf-reject6 - 6.6.95-r1
kmod-nf-tproxy - 6.6.95-r1
kmod-nfnetlink - 6.6.95-r1
kmod-nft-core - 6.6.95-r1
kmod-nft-fib - 6.6.95-r1
kmod-nft-nat - 6.6.95-r1
kmod-nft-offload - 6.6.95-r1
kmod-nft-tproxy - 6.6.95-r1
kmod-nls-base - 6.6.95-r1
kmod-nls-cp437 - 6.6.95-r1
kmod-nls-iso8859-1 - 6.6.95-r1
kmod-nls-utf8 - 6.6.95-r1
kmod-oid-registry - 6.6.95-r1
kmod-pcs-xpcs - 6.6.95-r1
kmod-phy-ax88796b - 6.6.95-r1
kmod-phy-microchip - 6.6.95-r1
kmod-phy-realtek - 6.6.95-r1
kmod-phy-smsc - 6.6.95-r1
kmod-phylink - 6.6.95-r1
kmod-ppp - 6.6.95-r1
kmod-pppoe - 6.6.95-r1
kmod-pppox - 6.6.95-r1
kmod-pps - 6.6.95-r1
kmod-ptp - 6.6.95-r1
kmod-r8169 - 6.6.95-r1
kmod-random-core - 6.6.95-r1
kmod-scsi-core - 6.6.95-r1
kmod-slhc - 6.6.95-r1
kmod-sound-core - 6.6.95-r1
kmod-stmmac-core - 6.6.95-r1
kmod-tg3 - 6.6.95-r1
kmod-tls - 6.6.95-r1
kmod-tpm - 6.6.95-r1
kmod-tun - 6.6.95-r1
kmod-udptunnel4 - 6.6.95-r1
kmod-udptunnel6 - 6.6.95-r1
kmod-usb-audio - 6.6.95-r1
kmod-usb-core - 6.6.95-r1
kmod-usb-ehci - 6.6.95-r1
kmod-usb-hid - 6.6.95-r1
kmod-usb-net - 6.6.95-r1
kmod-usb-net-asix - 6.6.95-r1
kmod-usb-net-asix-ax88179 - 6.6.95-r1
kmod-usb-net-cdc-eem - 6.6.95-r1
kmod-usb-net-cdc-ether - 6.6.95-r1
kmod-usb-net-cdc-mbim - 6.6.95-r1
kmod-usb-net-cdc-ncm - 6.6.95-r1
kmod-usb-net-cdc-subset - 6.6.95-r1
kmod-usb-net-dm9601-ether - 6.6.95-r1
kmod-usb-net-hso - 6.6.95-r1
kmod-usb-net-huawei-cdc-ncm - 6.6.95-r1
kmod-usb-net-ipheth - 6.6.95-r1
kmod-usb-net-lan78xx - 6.6.95-r1
kmod-usb-net-mcs7830 - 6.6.95-r1
kmod-usb-net-qmi-wwan - 6.6.95-r1
kmod-usb-net-rndis - 6.6.95-r1
kmod-usb-net-rtl8150 - 6.6.95-r1
kmod-usb-net-rtl8152 - 6.6.95-r1
kmod-usb-net-sierrawireless - 6.6.95-r1
kmod-usb-net-smsc75xx - 6.6.95-r1
kmod-usb-net-smsc95xx - 6.6.95-r1
kmod-usb-net-sr9700 - 6.6.95-r1
kmod-usb-serial - 6.6.95-r1
kmod-usb-serial-option - 6.6.95-r1
kmod-usb-serial-qualcomm - 6.6.95-r1
kmod-usb-serial-sierrawireless - 6.6.95-r1
kmod-usb-serial-wwan - 6.6.95-r1
kmod-usb-storage - 6.6.95-r1
kmod-usb-storage-extras - 6.6.95-r1
kmod-usb-storage-uas - 6.6.95-r1
kmod-usb-uhci - 6.6.95-r1
kmod-usb-wdm - 6.6.95-r1
kmod-usb-xhci-hcd - 6.6.95-r1
kmod-usb2 - 6.6.95-r1
kmod-usb3 - 6.6.95-r1
kmod-video-async - 6.6.95-r1
kmod-video-core - 6.6.95-r1
kmod-video-cpia2 - 6.6.95-r1
kmod-video-fwnode - 6.6.95-r1
kmod-video-gspca-core - 6.6.95-r1
kmod-video-pwc - 6.6.95-r1
kmod-video-uvc - 6.6.95-r1
kmod-video-videobuf2 - 6.6.95-r1
kmod-wireguard - 6.6.95-r1
lame-lib - 3.100-r1
less - 661-r1
libatomic1 - 13.3.0-r4
libattr - 2.5.2-r3
libblkid1 - 2.40.2-r1
libblobmsg-json20240329 - 2024.12.19~3868f47c-r1
libbz2-1.0 - 1.0.8-r1
libc - 1.2.5-r4
libcap-ng - 0.8.4-r1
libcares - 1.33.1-r1
libcomerr0 - 1.47.0-r2
libcurl4 - 8.12.1-r1
libdeflate - 1.22-r1
libdevmapper - 1.02.199
libdht - 2022.04.27~11123089-r1
libe2p2 - 1.47.0-r2
libev - 4.33-r2
libevent2-7 - 2.1.12-r2
libevent2-core7 - 2.1.12-r2
libevent2-pthreads7 - 2.1.12-r2
libext2fs2 - 1.47.0-r2
libf2fs6 - 1.16.0-r3
libfdisk1 - 2.40.2-r1
libffi - 3.4.7-r1
libffmpeg-full - 6.1.3-r1
libgcc1 - 13.3.0-r4
libgmp10 - 6.3.0-r1
libgnutls - 3.8.5-r1
libidn2 - 2.3.7-r1
libiwinfo-data - 2024.10.20~b94f066e-r1
libiwinfo20230701 - 2024.10.20~b94f066e-r1
libjpeg-turbo - 3.0.3-r1
libjson-c5 - 0.18-r1
libjson-script20240329 - 2024.12.19~3868f47c-r1
libkeyutils1 - 1.6.3-r2
liblucihttp-ucode - 2023.03.15~9b5b683f-r1
liblucihttp0 - 2023.03.15~9b5b683f-r1
liblz4-1 - 1.10.0-r1
liblzo2 - 2.10-r4
libmbedtls21 - 3.6.4-r1
libmicrohttpd-no-ssl - 1.0.1-r1
libminiupnpc - 2.2.8-r1
libmnl0 - 1.0.5-r1
libmount1 - 2.40.2-r1
libnatpmp1 - 20230423-r1
libncurses6 - 6.4-r2
libnettle8 - 3.9.1-r1
libnftnl11 - 1.2.8-r1
libnghttp2-14 - 1.63.0-r1
libnl-tiny1 - 2025.03.19~c0df580a-r1
libopenssl3 - 3.0.17-r1
libparted - 3.6-r1
libpcre2 - 10.42-r1
libpsl5 - 0.21.5-r1
libpthread - 1.2.5-r4
libreadline8 - 8.2-r2
librt - 1.2.5-r4
libsmartcols1 - 2.40.2-r1
libss2 - 1.47.0-r2
libssh2-1 - 1.11.0-r1
libstdcpp6 - 13.3.0-r4
libtirpc - 1.3.4-r1
libubox20240329 - 2024.12.19~3868f47c-r1
libubus20250102 - 2025.05.16~88e63250-r1
libuci20250120 - 2025.01.20~16ff0bad-r1
libuclient20201210 - 2024.10.22~88ae8f20-r1
libucode20230711 - 2025.05.11~d5b3a9dc-r1
libudebug - 2023.12.06~6d3f51f9
libunistring - 1.2-r1
libusb-1.0-0 - 1.0.27-r1
libustream-mbedtls20201210 - 2024.07.28~99bd3d2b-r1
libutp - 2023.02.14~c95738b1-r1
libuuid1 - 2.40.2-r1
libwrap - 7.6-r4
libx264 - 2024.05.13~4613ac3c-r1
logd - 2024.04.26~85f10530-r1
lsblk - 2.40.2-r1
luci - 25.196.48981~6781e95
luci-app-firewall - 25.196.48981~6781e95
luci-app-package-manager - 25.280.58373~8ce7b1e
luci-app-v2raya - 25.196.48981~6781e95
luci-base - 25.280.58391~b7e4a9c
luci-lib-uqr - 25.196.48981~6781e95
luci-light - 25.196.48981~6781e95
luci-mod-admin-full - 25.196.48981~6781e95
luci-mod-network - 25.273.68624~395e73d
luci-mod-status - 25.272.55957~0aae54f
luci-mod-system - 25.196.48981~6781e95
luci-proto-ipv6 - 25.196.48981~6781e95
luci-proto-ppp - 25.196.48981~6781e95
luci-proto-qmi - 25.196.48981~6781e95
luci-proto-sstp - 25.196.48981~6781e95
luci-proto-wireguard - 25.196.48981~6781e95
luci-theme-bootstrap - 25.196.48981~6781e95
mc - 4.8.32-r1
mkf2fs - 1.16.0-r3
motion-ffmpeg - 4.5.0-r1
mtd - 26
netifd - 2025.05.23~7901e66c-r1
nfs-kernel-server - 2.6.2-r4
nfs-kernel-server-utils - 2.6.2-r4
nfs-utils-libs - 2.6.2-r4
nftables-json - 1.1.1-r1
odhcp6c - 2024.09.25~b6ae9ffa-r1
odhcpd-ipv6only - 2024.05.08~a2988231-r1
openvpn-openssl - 2.6.14-r2
openwrt-keyring - 2024.11.01~fbae29d7-r2
opkg - 2024.10.16~38eccbb1-r1
parted - 3.6-r1
partx-utils - 2.40.2-r1
ppp - 2.5.1-r1
ppp-mod-pppoe - 2.5.1-r1
procd - 2024.12.22~42d39376-r1
procd-seccomp - 2024.12.22~42d39376-r1
procd-ujail - 2024.12.22~42d39376-r1
r8152-firmware - 20241110-r2
r8169-firmware - 20241110-r2
resolveip - 2
rp-pppoe-common - 4.0-r1
rpcbind - 1.2.6-r2
rpcd - 2024.09.17~9f4b86e7-r1
rpcd-mod-file - 2024.09.17~9f4b86e7-r1
rpcd-mod-iwinfo - 2024.09.17~9f4b86e7-r1
rpcd-mod-luci - 20240305-r1
rpcd-mod-rrdns - 20170710
rpcd-mod-ucode - 2024.09.17~9f4b86e7-r1
sms-tool - 2023.09.21~1b6ca032-r1
sstp-client - 1.0.20-r1
strongswan - 5.9.14-r7
terminfo - 6.4-r2
transmission-daemon - 4.0.6-r2
transmission-web - 4.0.6-r2
ubox - 2024.04.26~85f10530-r1
ubus - 2025.05.16~88e63250-r1
ubusd - 2025.05.16~88e63250-r1
uci - 2025.01.20~16ff0bad-r1
uclient-fetch - 2024.10.22~88ae8f20-r1
ucode - 2025.05.11~d5b3a9dc-r1
ucode-mod-fs - 2025.05.11~d5b3a9dc-r1
ucode-mod-html - 1
ucode-mod-math - 2025.05.11~d5b3a9dc-r1
ucode-mod-nl80211 - 2025.05.11~d5b3a9dc-r1
ucode-mod-rtnl - 2025.05.11~d5b3a9dc-r1
ucode-mod-ubus - 2025.05.11~d5b3a9dc-r1
ucode-mod-uci - 2025.05.11~d5b3a9dc-r1
uhttpd - 2023.06.25~34a8a74d-r4
uhttpd-mod-ubus - 2023.06.25~34a8a74d-r4
umbim - 2022.08.13~146bc77c-r25
uqmi - 2024.08.25~28b48a10-r2
urandom-seed - 3
urngd - 2023.11.01~44365eb1-r1
usb-modeswitch - 2022.02.24~3c8595a4-r1
usign - 2020.05.23~f1f65026-r1
v2raya - 2.2.7.1-r1
v4l2camera - 0.2.1-r2
wifi-scripts - 1.0-r1
wireguard-tools - 1.0.20210914-r4
wireless-regdb - 2025.02.20-r1
wwan - 2019.04.29-r6
xray-core - 25.1.30-r1
zlib - 1.3.1-r1
zoneinfo-core - 2025b-r1
I never edit any config manually, all settings are in their default values.
I now reinstalled https-dns-proxy and will reboot and see what happen. But I must say in previous cases of dead DHCP server it seems that https-dns-proxy is to blame, no matter if it is installed manually or as build-in package.
May be “config problem” in my case happen because packages “do not know” about each other, and have their config files not correspond with each other, for I did not installed https-dns-proxy manually I just include it in my build of OpenWRTwuth help of make menuconfig
I believe doh_backup_server could be blank for it is backup server - a necessary, but not obligatory setting and can not influence stability or cause critical failures
you have to choose which one to use:
You installed this:
It's not fair to have more than one "doh/dot" system installed. Choose which one to use.
opkg search `which doh-client`
root@OpenWrt:~# opkg search which doh-client
dns-over-https - 2.3.0-r2
root@OpenWrt:~#
You have to get that away from port 53 too.
I guess I was thinking all is part of one package that is why I installed them. But I surely remember that when I use original image of OpenWRt from this site I also happen to have DHCP problems. Yet may be they were caused by different reasons
I wonder how dnsproxy conflict with dnsmasq? I mean dnsproxy is DNS caching server, it should not interact with 53 port?
ask dnsproxy?
[OpenWrt Wiki] DoH/DoH3, DoT, DoQ and DNSCrypt with Dnsmasq and dnsproxy So this is official way to encript DNS queries? I then remove all other solutions and install only this