No dns -- DNS_PROBE_FINISHED_BAD_CONFIG

No operable internet as receiving message above.
Dual boot machine and dns/internet works fine on windows. Likely eliminates router and isp as windows internet works

Tried to clear dns cache but ncsd is not located where references said it was. Could use an update on how to clear dns cache.

I switched from networkmanager to wicked and back.
I added some new dns settings. Nothing working thus far.

Anyone with updates/diagnostic steps? Anyone having similar issues?
I did try going back one kernel; did not work. I also tried different desktops; did not work.

Any guidance? Thanks, tom kosvic

Where? From Where? When doing what? Crystal globe fails.

Message in title of thread shows on every browser webpage after you enter or select any URL. Same on vivaldi, brave, firefox

Message accompanied by: “This page can’t be reached”

@tckosvic cat /etc/resolv.conf and cat /etc/nsswitch.conf

Sorry Malcolm but can only work from tablet and can’t copy/paste.

Resolve, conf has 3 active lines:
Nameserver 127,0.0.53
Options edns0 trust-ad
Search lan

Nsswitch has one interesting line. See below. `

Hosts: files mdns_minimal [NOTFOUND=Return] dns
Networks: files dns

Rest is too long to type it all

Assuming you have problems discerning commas from dots when typing, this seems to be the local system?

What should be the DNS system to be used?

The dns should be default. I think 1.1.1.1 but could be 8.8.8.8 which i think is google dns, i could find out what dns windows is using successfully. I will do that and report the answer.

Then set opensuse dns to be the same. I need a reference for where to enter leap dns settings.

Thanks, tom kosvic

It all depends how you did setup your network. With Networkmanager a proper entry may look like this when a FritzBox serves as DHCP server (the DNS server is set in the FritzBox itself and the IP shown in the output is the FritzBox IP in the local LAN):

:~> cat /etc/resolv.conf
# Generated by NetworkManager
search fritz.box
nameserver 192.168.178.1

If you don’t use a router which provides the DNS adress, you need to set them on your machine.
As said…it highly depends on your setup.

Windows boot on same computer shows:
Dns servers

2603:8081:1603:49ae::1 and also
192.168.1.1

My internet comes in through cable company router. things have worked for years with no changes. But something has happened.

Windows internet works, openSUSE does not on same ethernet.

Plan is to search references and do reinstall of dns config files. If that is unsuccessfuk, I have timeshift snapshot from when dns was working and I will do a restore,

With no internet, I can’t zypper in anything.

Tom kosvic

@tckosvic:

There’s this discussion – <YaST not saving or even applying static ip routes>

Please note that, if in ‘/etc/sysconfig/network/config’ the parameter “NETCONFIG_DNS_FORWARDER” isn’t set to the value “resolver” when neither a BIND server nor a dnsmasq server is setup, then various strange DNS resolution effects will be seen on your system –

  • Could be a possible cause for the failed resolution of the address “8.8.8.8” to “dns.google” …

And, for completeness – a non-Network-Manager system –

 > file /etc/resolv.conf
/etc/resolv.conf: symbolic link to /run/netconfig/resolv.conf
 > 
 > cat /etc/resolv.conf 
### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
search fritz.box
nameserver 192.168.178.1
nameserver fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e
nameserver 2001:9e8:ab40:6e00:62b5:8dff:fefe:ca0e
 >

Various comments from @tckosvic :slight_smile:

Hmm. So you switched:
NetworkManager to Wicked, then:
Wicked to NetworkManager, then:
NetworkManager to Wicked

So, you’re now using Wicked.

It’s very important to follow each “switch step” required to switch from one to the other.

It you missed a step, or executed a switch incorrectly, you may have a mix of both options.

Nameserver is “127,0.0.53” <== using a comma is incorrect.

“which” line is interesting? You show two lines.
The only one I can comment on is “[NOTFOUND=Return]”
The word “Return” should be “return”. (Linux is notoriously case-sensitive)

“1.1.1.1” is provided by Cloudflare (not your provider),
and which is not Google DNS, which is “8.8.8.8” (primary address).

Technically, Google DNS addresses should be: “8.8.8.8 and 8.8.4.4” for IPV4,
… and for IPV6 as: “2001:4860:4860::8888 and 2001:4860:4860::8844”
.
Final comment (wild guess) … I suspect the multiple switches between NetworkManager and Wicked is the cause of the issue.

DNS problem is solved.

Out of a lack of patience, I did a restore of “timeshift” backup from 7/17/2025. After reboot the browsers are all opening websites selected by a search or by entering a URL.
Thunderbird email is working also. zypper from terminal is also working and downloading patches and updates.

Trouble with this solution is I don’t know what was broken and what got fixed. I did nothing that would have caused this DNS problem and I still don’t know how to prevent it from happening again.

It does appear, however, that restoring a “timeshift” snapshot will fix it.

thanks, tom kosvic

The package description tells all:

erlangen:~ # zypper if wicked
Loading repository data...
Reading installed packages...


Information for package wicked:
-------------------------------
Repository     : oss
Name           : wicked
Version        : 0.6.78-1.2
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 3.9 MiB
Installed      : No
Status         : not installed
Source package : wicked-0.6.78-1.2.src
Upstream URL   : https://github.com/openSUSE/wicked
Summary        : Network configuration infrastructure
Description    : 
    Wicked is a network configuration infrastructure incorporating a number
    of existing frameworks into a unified architecture, providing a DBUS
    interface to network configuration.

erlangen:~ # 

wicked is a rich and never-ending source of annoyances. Deinstall and make sure it doesn’t install again.

@Everyone:

“Wicked” is a network configuration infrastructure which waits until the IPv6 handshaking and address assignment has completed at boot time.

  • If, this isn’t an issue for your Use Case then, feel free to use something else … :smiling_imp:
1 Like

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