[GH-ISSUE #578] Bug: No clear reason why not being set as default dns #190

New issue

Closed

opened 2026-02-26 04:34:20 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 04:34:20 +03:00

Owner

Originally created by @mageddo on GitHub (Sep 25, 2024).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/578

What is Happening

11:43:11.065 [Thread-2       ] INF c.m.d.dnsconfigurator.DnsConfigurators            l=113  m=getInstance0                    usingDnsConfigurator=DnsConfiguratorLinux
11:43:11.066 [Thread-2       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=91   m=lambda$findBestConfFile$0       status=noValidConfFile, file=/host/etc/systemd/resolved.conf
11:43:11.066 [Thread-2       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=91   m=lambda$findBestConfFile$0       status=noValidConfFile, file=/host/etc/resolv.conf
11:43:11.066 [Thread-2       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=91   m=lambda$findBestConfFile$0       status=noValidConfFile, file=/etc/systemd/resolved.conf
11:43:11.066 [Thread-2       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=91   m=lambda$findBestConfFile$0       status=noValidConfFile, file=/etc/resolv.conf
11:43:11.066 [Thread-2       ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=122  m=init                            status=using, configFile=null

What is Expected

Log what is the cause the file couldn't be used to configure DPS as default DNS

Specs

DPS Version: latest in current date

Originally created by @mageddo on GitHub (Sep 25, 2024). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/578 ## What is Happening ``` 11:43:11.065 [Thread-2 ] INF c.m.d.dnsconfigurator.DnsConfigurators l=113 m=getInstance0 usingDnsConfigurator=DnsConfiguratorLinux 11:43:11.066 [Thread-2 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=91 m=lambda$findBestConfFile$0 status=noValidConfFile, file=/host/etc/systemd/resolved.conf 11:43:11.066 [Thread-2 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=91 m=lambda$findBestConfFile$0 status=noValidConfFile, file=/host/etc/resolv.conf 11:43:11.066 [Thread-2 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=91 m=lambda$findBestConfFile$0 status=noValidConfFile, file=/etc/systemd/resolved.conf 11:43:11.066 [Thread-2 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=91 m=lambda$findBestConfFile$0 status=noValidConfFile, file=/etc/resolv.conf 11:43:11.066 [Thread-2 ] INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=122 m=init status=using, configFile=null ``` ## What is Expected Log what is the cause the file couldn't be used to configure DPS as default DNS ## Specs * DPS Version: latest in current date

kerem

2026-02-26 04:34:20 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 04:34:20 +03:00

Author

Owner

@mageddo commented on GitHub (Oct 7, 2024):

Fixed at #585 .

Log example

INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux  l=98   m=lambda$findBestConfFile$0 status=noValidConfFile, file=/host/etc/resolv.conf, condition=PathExistsPredicate

@mageddo commented on GitHub (Oct 7, 2024): Fixed at #585 . Log example ``` INF c.m.d.dnsconfigurator.linux.DnsConfiguratorLinux l=98 m=lambda$findBestConfFile$0 status=noValidConfFile, file=/host/etc/resolv.conf, condition=PathExistsPredicate ```