[opensuse] DNS not working on 15.0
This morning I noticed a problem with DNS resolution on my ThinkPad E520. I am not able to resolve host names. However, other devices, connected to the same network work OK. Even Windows 10, in a virtual machine on this computer, works fine. With Wireshark, I see no DNS packets, even when I use the host command. Resolv.conf doesn't list any DNS servers. This computer uses network manager and the problem occurs with both Ethernet and WiFi. I can ping by IP address, but not host name. I checked all the settings I could think of and nothing seems amiss. The only thing I can think of that might have caused this is some recent updates, but not sure. Any ideas? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Further on this. If I manully add a DNS to resolv.conf, I can resolve host names. I have also used Wireshark, to verify DHCP provides the DNS addresses. For some reason, they're not being added to resolv.conf. On 09/11/2018 01:59 PM, James Knott wrote:
This morning I noticed a problem with DNS resolution on my ThinkPad E520. I am not able to resolve host names. However, other devices, connected to the same network work OK. Even Windows 10, in a virtual machine on this computer, works fine. With Wireshark, I see no DNS packets, even when I use the host command. Resolv.conf doesn't list any DNS servers. This computer uses network manager and the problem occurs with both Ethernet and WiFi. I can ping by IP address, but not host name. I checked all the settings I could think of and nothing seems amiss. The only thing I can think of that might have caused this is some recent updates, but not sure.
Any ideas?
tnx jk
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/11/18 1:59 PM, James Knott wrote:
This morning I noticed a problem with DNS resolution on my ThinkPad E520. I am not able to resolve host names.
<snip>
Any ideas?
As of when I dug through something similar about a week ago... this sounds like a known intermittent failure in Network Management-Land. Seems environment and sequence-dependent, though not clear how. Work-Arounds mostly amount to: "Kick it in the head to make it re-figure it's configurations." The most common is "Remove resolv.conf, n force it to refigure (network management command, or reboot.)" The second most frequent suggestion is placing a known, good DNS address in resolv.conf, usually: 8.8.8.8. I DONT KNOW ENTIRELY WHAT EITHER OF THESE DO. I am not a network-wrangler, nor do I play one on TV. YMMV. Here Be Dragons. Free Advice is Worth What You Pay For It. Resources: -- A prior, recent disucssion on this list of "can't connect to WiFi" sounds similar, with the common "fixes". -- Problem / solution threads in the OpenSuSE forums address this. Also point to some general network diagnostic sequences. -- Bugzilla bugs for NetworkManager, which on this one amounted to "Not sure what this is, yet." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/11/2018 03:13 PM, jbullock wrote:
Work-Arounds mostly amount to: "Kick it in the head to make it re-figure it's configurations." The most common is "Remove resolv.conf, n force it to refigure (network management command, or reboot.)"
The second most frequent suggestion is placing a known, good DNS address in resolv.conf, usually: 8.8.8.8.
I DONT KNOW ENTIRELY WHAT EITHER OF THESE DO. I am not a network-wrangler, nor do I play one on TV. YMMV. Here Be Dragons. Free Advice is Worth What You Pay For It.
I can certainly try removing resolv.conf and see what happens. However, I'll try rebooting, as I currently have a known, good address in it, my firewall/router. Hang on a minute while it reboots. . . . Nope, the DNS addresses haven't been added. I'll try removing resolv.conf. Hang on again . . . That did it. Hopefully it will stay. I'll try with a different connection to make sure it still works. Yep. Well that appears to fix it for now. tnx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2018 15.23, James Knott wrote:
On 09/11/2018 03:13 PM, jbullock wrote:
Work-Arounds mostly amount to: "Kick it in the head to make it re-figure it's configurations." The most common is "Remove resolv.conf, n force it to refigure (network management command, or reboot.)"
The second most frequent suggestion is placing a known, good DNS address in resolv.conf, usually: 8.8.8.8.
I DONT KNOW ENTIRELY WHAT EITHER OF THESE DO. I am not a network-wrangler, nor do I play one on TV. YMMV. Here Be Dragons. Free Advice is Worth What You Pay For It.
I can certainly try removing resolv.conf and see what happens. However, I'll try rebooting, as I currently have a known, good address in it, my firewall/router.
Remove file, restart network, should work. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 11 september 2018 22:10:07 CEST schreef Carlos E. R.:
On 11/09/2018 15.23, James Knott wrote:
On 09/11/2018 03:13 PM, jbullock wrote:
Work-Arounds mostly amount to: "Kick it in the head to make it re-figure it's configurations." The most common is "Remove resolv.conf, n force it to refigure (network management command, or reboot.)"
The second most frequent suggestion is placing a known, good DNS address in resolv.conf, usually: 8.8.8.8.
I DONT KNOW ENTIRELY WHAT EITHER OF THESE DO. I am not a network-wrangler, nor do I play one on TV. YMMV. Here Be Dragons. Free Advice is Worth What You Pay For It.
I can certainly try removing resolv.conf and see what happens. However, I'll try rebooting, as I currently have a known, good address in it, my firewall/router.
Remove file, restart network, should work. Proper way: sudo netconfig -f update
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Knurpht-openSUSE composed on 2018-09-12 02:57 (UTC+0200):
Remove file, restart network, should work.
Proper way: sudo netconfig -f update
For Wicked, NetworkManager, or both? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 12 september 2018 03:16:17 CEST schreef Felix Miata:
Knurpht-openSUSE composed on 2018-09-12 02:57 (UTC+0200):
Remove file, restart network, should work.
Proper way: sudo netconfig -f update
For Wicked, NetworkManager, or both? Both
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
<snip>
Remove file, restart network, should work. Proper way: sudo netconfig -f update
That's the command I didn't have near to hand or top of mind. One can't be deeply involved on everything. Glad there are experts around. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
This has been bugging me intermittently for quite some time, most often zypper updating. Retry is often enough, but sometimes it takes a reboot. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/11/18 7:53 PM, Felix Miata wrote:
This has been bugging me intermittently for quite some time, most often zypper updating. Retry is often enough, but sometimes it takes a reboot.
When I dug throught Bugzilla, the developers / maintainers don't quite have enough to chase this one down. In my case, same conditions, 42.2 did fine, while 15.0 borked itself -- fits with the timing of when this reports of something like this behavior appeared. Adds nothing; they already have a notion when it started happening. The developers / maintainers are talking "race condition" in the bug notes. You gotta get pretty granular and on point to provide info to unwind one of those. Anybody have an idea what factoids might help them run this down? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/17/2018 11:22 PM, jbullock wrote:
The developers / maintainers are talking "race condition" in the bug notes. You gotta get pretty granular and on point to provide info to unwind one of those.
Anybody have an idea what factoids might help them run this down?
There isn't any "silver-bullet" factoid that will help the devs correct a race condition. It is a code screwup somewhere in 800,000 lines of multi-threaded (or otherwise parallel executed) code that leads to two treads attempting to access a shared bit of memory (or shared value) and there is some fault with the locking (or condition locks) so that a required thread is effectively prevented from executing the code it needs to run to complete whatever it is trying to do. If things are not moving quickly on the bug, it is because the code involved may be voluminous, what condition or which of the myriad of locks is the cause is anything but clear, and it will take many hours of tedious debugging to find out where in the daisy-chain of locking logic the problem is hiding. You can read more about what a "data race" is and what a "race condition" is here: What is a race condition? https://stackoverflow.com/questions/34510/what-is-a-race-condition -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/18/18 4:26 AM, David C. Rankin wrote:
On 09/17/2018 11:22 PM, jbullock wrote:
The developers / maintainers are talking "race condition" in the bug notes. You gotta get pretty granular and on point to provide info to unwind one of those.
Anybody have an idea what factoids might help them run this down?
There isn't any "silver-bullet" factoid that will help the devs correct a race condition.
<snip> Thats why I asked. I could try to reproduce the failure n grab something useful, if there's something that might be useful. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Quoting jbullock <jbullock@rare-bird-ent.com>: [snip]
The second most frequent suggestion is placing a known, good DNS address in resolv.conf, usually: 8.8.8.8.
8.8.8.8 is the Google DNS server address.
I DONT KNOW ENTIRELY WHAT EITHER OF THESE DO. I am not a network-wrangler, nor do I play one on TV. YMMV. Here Be Dragons. Free Advice is Worth What You Pay For It.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Jeffrey L. Taylor wrote:
Quoting jbullock <jbullock@rare-bird-ent.com>: [snip]
The second most frequent suggestion is placing a known, good DNS address in resolv.conf, usually: 8.8.8.8.
8.8.8.8 is the Google DNS server address.
8.8.4.4 is the 2nd one. Cloudflare offers 1.1.1.1 and 1.0.0.1 -- Per Jessen, Zürich (18.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/09/2018 02.44, Per Jessen wrote:
Jeffrey L. Taylor wrote:
Quoting jbullock <jbullock@rare-bird-ent.com>: [snip]
The second most frequent suggestion is placing a known, good DNS address in resolv.conf, usually: 8.8.8.8.
8.8.8.8 is the Google DNS server address.
8.8.4.4 is the 2nd one.
Cloudflare offers 1.1.1.1 and 1.0.0.1
A bug on some routers blocks using Cloudflare addresses, but last time I heard Telefonica was preparing a patch for their routers. They finally accepted their error. They used the IP internally as if it were non routable. And they were not the only ones doing it. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/11/2018 10:47 PM, Jeffrey L. Taylor wrote:
The second most frequent suggestion is placing a known, good DNS address in resolv.conf, usually: 8.8.8.8.
8.8.8.8 is the Google DNS server address.
I often use that for testing in my work. However, I set it to my own firewall address of 172.16.0.1. Anyone else is free to use it, if they want. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Carlos E. R. -
David C. Rankin -
Felix Miata -
James Knott -
jbullock -
Jeffrey L. Taylor -
Knurpht-openSUSE -
Per Jessen