Ask Your Question
0

KDE: DNS problems, orange exclamation mark on systray icon

asked 2015-06-01 22:28:15 -0600

Matthew Cline gravatar image

updated 2015-06-02 04:18:35 -0600

Since upgrading to Fedora 22, I've intermittentaly had DNS problems, and when this occurs there's always an orange exclamation mark on the KDE/Plasma networking system tray icon. Using the icon's popup menu to display more details for the connection gives no insights. Grepping /var/log/messages for DNS shows nothing interesting. chrome and ping report it as a timeout, while dig reports it as not being able to find any DNS servers. ping -n and mtr -n have no problem reaching the two nameservers listed in /etc/resolve/conf, so I don't know why there's this problem.

My Linux machine uses a wireless connection. A Windows 7 machine which is directly/non-wirelessly connected to the XFinity wireless router (and which uses the same nameservers as my Linux machine) can use DNS, but while the Linux DNS problem persists the Windows name lookups seem to take longer than normal, and Chrome intermittently gives DNS errors like DNS_PROBE_FINISHED_BAD_CONFIG, DNS_PROBE_FINISHED_NXDOMAIN and DNS_PROBE_STARTED.

I've tried the following solutions, all to no avail:

  • Use the systray icon network popup menu to disconnect and reconnect to the wireless router.
  • Use /etc/rc.d/init.d/network to stop and restart networking.
  • Removing and reinsterting the USB wireless network device.
  • Disabling the firewall.
  • Restarting the avahi demon.
  • Editing /etc/nsswitch.conf to skip mDNS and go directly to DNS.
  • Rebooting the computer.
  • Doing a soft-reset of the XFinity wireless router.
edit retag flag offensive close merge delete

Comments

Two questions. First, is your Fedora box using the same DNS servers as your Windows box? Second, can you ping 23.202.254.127? (It's a site I use that I know responds properly to pings.) If you can reach out and ping by IP, it's not a connectivity or routing issue; if you can't, try using traceroute.

sideburns gravatar imagesideburns ( 2015-06-02 01:13:49 -0600 )edit

1) They both use the same nameservers 2) the problem is gone for the moment, so I can't test if there's a routing problem

Matthew Cline gravatar imageMatthew Cline ( 2015-06-02 04:21:32 -0600 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2016-11-30 08:41:38 -0600

john012 gravatar image

Very interesting your question about error "Could not find the DNS address of the server ." To solve this problem, try one or more of the following methods.

Restore the IP address . If the network uses DHCP, you can get a new IP address of the computer. You may need to do this if you are having connection problems. 1. Press the key Windows + X, and then click Command Prompt in the search box , click Command Prompt . 2. At the command prompt, type ipconfig / release and press Enter. This releases your current IP address. 3. At the command prompt, type ipconfig / renew and press Enter to get the new IP address.

The DHCP configuration will be renewed for all adapters. To renew the IP address for a specific adapter, type the adapter name that appears when you type ipconfig at the command prompt. Restart the computer and test and see if the behavior, remaining the same behavior change the DNS to assess whether the current DNS is causing this behavior.

Change DNS. 1. Click Control Panel , Network and Internet , Network and Sharing Center;
2. In Network and Sharing Center click Change adapter settings;
3. Now click with the right mouse button over ethernet and select Properties will open the window Ethernet Properties select TCP / IPv4 click the button Properties.
4. In the tab General Select Use the following DNS addresses:

• Preferred DNS server: 4.2.2.2
• Alternate DNS server: 4.2.2.4

Test and see if the behavior is repeated. Disable Proxy. Click the key Windows + R Type inetcpl.cpl , and then click OK. Click Connections. Click the Lan Settings. Then uncheck the Use a proxy server for your network loc al. Click Apply. Leave only checked the Automatically detect settings. Create a new user account to see if the user profile was not corrupted. 1. Press the key Windows + X ; 2. Select the Command Prompt (Admin) ; 3. In the Command Prompt, type the following lines: net user test / add (enter) net localgroup administrators test / add (enter) Or otherwise try this: http://www.deskdecode.com/dns_probe_f...

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2015-06-01 22:28:15 -0600

Seen: 927 times

Last updated: Jun 02 '15